Skip to main content
NetApp Knowledge Base

NFS client hang up if storage reply NFS4ERR_DELAY followed by NFS4ERR_SEQ_MISORDERED

  1. Last updated
  2. Save as PDF
Views:
1,748
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFSv4.1
  • pNFS
  • RedHat Enterprise Linux (RHEL)

Issue

  • After a network partition (network is unavailable for some time) Linux clients can be seen to lose track of NFS4.1 Sequencing
  • After the network has recovered, the NFS client has incremented its sequence on the active slot beyond where the server has acknowledged
    • This is an indication that multiple sequences have been sent and not retransmitted as the server never receives the missed sequences
 

 

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.