NetApp NFS server running Ontap 9.2 incorrectly responds to LOCKU with NFS4ERR_BAD_SEQID (10026) and 'bad sequence-id' errors seen in messages file on Linux NFS client

Solution Unverified - Updated -

Issue

  • We upgraded our NetApp filer to Ontap 9.2 and are now seeing a lot of bad sequence-id error on an unconfirmed sequence messages. A tcpdump shows LOCKU can get a response of NFS4ERR_BAD_SEQID (10026) and after that, RELEASE_LOCKOWNER gets a response of NFS4ERR_LOCKS_HELD (10037).

Environment

  • NetApp NFS server
    • seen on Ontap 9.2
  • Red Hat NFS client
    • seen on RHEL6.9 (kernel-2.6.32-696.10.3.el6)
  • 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