NFSv4.1: NFS server returns NFS4ERR_OLD_STATEID for NFS client opening/closing files in rapid succession

Solution Verified - Updated -

Issue

  • After migrating from NFSv3 to NFSv4.1, a third-party NFS server reports a RHEL NFS client as using an old sequence number for a stateid sequence id.
  • The NFS server logs the NFS client as using an incorrect sequence id for a given stateid, but uses the correct sequence id after receiving NFS4ERR_OLD_STATEID.
  • The NFS client reports no errors and there are no application issues accessing the NFS share.

Environment

  • Red Hat Enterprise Linux (NFS client)
    • RHEL 7.3 and later
    • RHEL 8
  • NFSv4.1 or later
  • Any NFS server.

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