Re: Seemingly inconsistent directory state under NFSv4

["J. Bruce Fields" <bfields@fieldses.org>]

By the way, could you configure your mail client not to drop me (or
others) off the cc:?  Those of us that subscribe to a lot of high-volume
kernel lists generally treat mail sent to us diferently from mail sent
to a list.

On Thu, Feb 24, 2011 at 05:48:58PM +0100, Ferenc Wagner wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
> One client removed the file, and another could still access it by name
> (although not present in the directory listing).  So it could have been
> a client-client conflict, even though we couldn't prove that the removed
> file was actually in use on the client.  Is there a way to list the
> delegations being hold by a client?

Not really.  They'll show up as LEASE entries in /proc/locks, with the
pid of an nfsd process, but no way to associate them with a client.

Some way to dump lock (and other state) information might be a nice
thing to have some day for debugging and tuning.

> > You can turn off delegations completely with
> > 	echo 0 >/proc/sys/fs/leases-enable
> > before starting the nfs server.
> 
> Wouldn't I lose most of the efficiency advantages of NFSv4 with that
> move?

Probably so.  It would at least be a way to verify whether delegations
are the source of your problem, if you have a reproduceable test case.

--b.