Skip to main content
NetApp Knowledge Base

NFSv4 access issue with a bad sequence-id error

Views:
1,101
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFSv4

Issue

  • NFSv4 client reports the following error
vm01 kernel: [528489.817903] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff89721ba18e20
  • Reboot the client can workaround to mitigate the error for some time
  • EMS log would show BAD_SEQID error 
node01: kernel: nblade.nfs4sequenceinvalid:NOTICE]: NFS client (IP: 10.10.10.100) sent sequence# 104017726, but server expected sequence# 103564588. Server error: BAD_SEQID.

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.