Skip to main content
NetApp Knowledge Base

NFS4 Lock reclaim failed error when using NFS4.1

Views:
681
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nfs
Last Updated:

Applies to

  • ONTAP 9.5 and earlier
  • NFS 4.1

Issue

  • Linux clients report the following message in their logs:  nfs4_reclaim_open_state: Lock reclaim failed!
  • A packet trace collected while the issue is occurring reveals the following:

Example:

708813 2020-05-18 18:04:42.081399 0.000015 XXX.XXX.XX.1 XXX.XXX.XX.2 NFS 290  0xbf4f8e90 V4 Call (Reply In 708820) OPEN FH: 0xbf4f8e90
708815 2020-05-18 18:04:42.081433 0.000018 XXX.XXX.XX.1 XXX.XXX.XX.2 NFS 246 196415223 0xbf4f8e90 V4 Call (Reply In 708818) CLOSE StateID: 0xfb5d
708818 2020-05-18 18:04:42.081603 0.000032 XXX.XXX.XX.2 XXX.XXX.XX.1 NFS 250 0 0xbf4f8e90 V4 Reply (Call In 708815) CLOSE
708820 2020-05-18 18:04:42.081674 0.000063 XXX.XXX.XX.2 XXX.XXX.XX.1 NFS 414 196415231 0xbf4f8e90 V4 Reply (Call In 708813) OPEN StateID: 0xda05
708821 2020-05-18 18:04:42.081734 0.000060 XXX.XXX.XX.1 XXX.XXX.XX.2 NFS 294 196415231 0xbf4f8e90 V4 Call (Reply In 708824) LOCK FH: 0xbf4f8e90 Offset: 0 Length: <End of File>
708824 2020-05-18 18:04:42.082221 0.000355 XXX.XXX.XX.2 XXX.XXX.XX.1 NFS 166  0xbf4f8e90 V4 Reply (Call In 708821) LOCK Status: NFS4ERR_BAD_STATEID

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support