RHEL6 NFSv4 client keeps using the stale stateid after current clientid is obtained

Solution Verified - Updated -

Issue

  • NFSv4 client keeps using the stale stateid after current clientid is obtained

  • While testing nfs client with ganesha NFS server (NFSv4), we have encountered a number of incidences where the client keeps using the stale stateid (stateid obtined in the previous clientid incarnation), though it already has the new clientid.

Environment

  • Red Hat Enterprise Linux (RHEL) (NFS client)
    • Seen on RHEL6.2 (2.6.32-220.*el6) and RHEL6.3 (2.6.32-279.*el6) kernels
  • NFSv4
  • ganesha NFS server

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.