Skip to main content
NetApp Knowledge Base

EMS error nblade.nfs4SequenceInvalid

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

Applies to

  • ONTAP 9
  • NFSv4.x

Issue

  • NFSv4 client logs a message similar to 
    • NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence.
    • vm01 kernel: [528489.817903] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff89721ba18e20
  • NFSv4 client may or may not be disrupted
    • Most clients should be able to auto-recover from this issue.
  • EMS logs some variant of nblade.nfs4SequenceInvalid
  • kernel nblade.nfs4SequenceInvalid: NFS client (IP: X.X.X.X) sent sequence# 3, but server expected sequence# 4. Server error: OLD_STATEID
  • 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.