NetApp NFS server running Ontap 9.1P1 C-mode incorrectly responds to OPEN, CLOSE, or OPEN_CONFIRM with NFS4ERR_BAD_SEQID (10026) and 'bad sequence-id' errors seen in messages file on Linux NFS client

Solution Verified - Updated -

Issue

NFSV4 share on Netap hangs when attempt to read or write file at some point of time. This issue occurred twice today. At the same time we noticed "NFS Store Pool for String exhausted" on the netapp storage. Once we migrate LIF at storage end issue gos away for a while. We noticed NFS errors kernel: NFS: v4 server XYZ returned a bad sequence-id error! at the time of issue.

Environment

  • Red Hat Enterprise Linux (NFS Client)
    • seen on RHEL7.4 kernel 3.10.0-693.2.1.el7
  • NetApp (NFS server)
    • seen on Ontap 9.1P1 C-mode
  • seen on NFS4.0

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