NFS locks may not be released when a process is killed with signal, causing future locking failures

Solution In Progress - Updated -

Issue

  • Periodically, NFS locks may not be released when a process is killed with signal, resulting in a mismatched state where the server believes the client holds the lock, but the client believes the lock has been released. The result is that further locks are blocked.

Environment

  • Red Hat Enterprise 6.6 NFS client
    • NFSv3 mount

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