Skip to main content
NetApp Knowledge Base

nfs4SequenceInvalid error with Server error BAD_SEQID in EMS

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

Applies to

  • ONTAP 9
  • NFSv4.0

Issue

  • Bad-sequence-id errors started after ONTAP upgrade
  • Performance impacts due to file locks may be seen.
  • EMS log:

[nas1: kernel: ems.engine.suppressed:debug]: Event 'nblade.nfs4SequenceInvalid' suppressed 7 times in last 257 seconds.[nas1: kernel: nblade.nfs4SequenceInvalid:notice]: NFS client (IP: 1.2.3.4) sent sequence# 6, but server expected sequence# 7. 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.