NFS locks may not be released when a process is killed with signal, causing future locking failures
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 of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.