Why can't a second NFSv3 client obtain a lock on a file after the first client crashed?

Solution Verified - Updated -

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.

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