NetApp NFS server returns NFS4ERR_BAD_SEQID (10026) and 'bad sequence-id' errors seen in messages file due to previous OPEN or CLOSE completing with an error

Solution Verified - Updated -

Issue

  • In the NFS client's messages file we see error messages indicating bad sequence-id
May  1 09:41:30 localhost kernel: NFS: v4 server mynfsserver  returned a bad sequence-id error!
  • A tcpdump shows NFS4ERR_BAD_SEQID (10026) and prior to that, some OPEN, CLOSE, or other locking operation completing with a different error code such as NFS4ERR_NOSPC or NFS4ERR_ADMIN_REVOKED

Environment

  • Red Hat Enterprise Linux (NFS client)
  • NetApp (NFS server)
    • Seen on Data Ontap 8.2.3
    • Seen on Data Ontap 8.2.2P2 7-Mode
  • NFS4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content