Why can't a second NFSv3 client obtain a lock on a file after the first client crashed?
Issue
After a crash (like a kernel panic) or network-split of a NFSv3 client that holds a lock on a file, an other client can not obtain the lock.
Environment
- Red Hat Enterprise Linux 4, 5, 6
- Red Hat Storage 2.0, 2.1
- Network Filesystem version 3 (NFSv3)
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.