Skip to main content
NetApp Knowledge Base

NFSv4 client hung after TO/GB with NFS4ERR_STALE_CLIENTID

Views:
527
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • NFSv4.x
  • ONTAP 9

Issue

  • A network trace collected at time of an NFSv4 client hung after an ONTAP Takeover/Giveback contains "NFS4ERR_STALE_CLIENTID" error being returned by ONTAP
  • The client is unable to recover ending in a loop with "NFS4ERR_STALE_CLIENTID" being repeated

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.