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
- 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, tools, and much more.
