RHEL6 / RHEL7: NFS4 client receiving NFS4ERR_BAD_SEQID drops nfs4 stateowner resulting in infinite loop of READ/WRITE + NFS4ERR_BAD_STATEID

Solution Verified - Updated -


NFS4 client hangs and must be rebooted after seeing one or more bad sequence-id error messages


  • Red Hat Enterprise Linux 6 (NFS4 client)
    • kernels prior to kernel-2.6.32-696.16.1.el6
  • Red Hat Enterprise Linux 7 (NFS4 client)
    • all kernels before 3.10.0-693.el7 (RHEL7.4) affected
  • Seen with NetApp NFS server (other servers likely affected)

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