Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Dec 2016 07:30:45 +0000
From:      Colin Percival <cperciva@tarsnap.com>
To:        Rick Macklem <rmacklem@uoguelph.ca>, Benjamin Kaduk <kaduk@mit.edu>
Cc:        "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   Re: ESTALE after cwd deleted by same NFS client
Message-ID:  <01000158fc3d9bab-65b7741f-ca02-4024-a34c-b8be22a3b5e6-000000@email.amazonses.com>
In-Reply-To: <YQBPR01MB018054EE62DEFDC73784AD9BDD9B0@YQBPR01MB0180.CANPRD01.PROD.OUTLOOK.COM>
References:  <01000158f023675b-41b35a73-4428-4937-853b-62db4fb9b984-000000@email.amazonses.com> <20161212054233.GU8460@kduck.kaduk.org> <01000158f1abc081-d4eddc58-3b4b-41dd-aa1e-0157d2fad812-000000@email.amazonses.com> <20161212163603.GV8460@kduck.kaduk.org> <YQBPR01MB018054EE62DEFDC73784AD9BDD9B0@YQBPR01MB0180.CANPRD01.PROD.OUTLOOK.COM>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/13/16 05:04, Rick Macklem wrote:
>>>> On Sun, Dec 11, 2016 at 11:06:42PM +0000, Colin Percival wrote:
>>>>> If I run the following with /nfs/ being an NFS mount:
>>>>> # mkdir /nfs/foo
>>>>> # touch /nfs/foo/bar
>>>>> # cd /nfs/foo
>>>>> # rm -r /nfs/foo
>>>>> # rm bar
> If this is happening on a single client

Yes.  At the time I ran this, there was only one client.

> something is broken.
> - For this step, the name cache should have a miss and the Lookup should fail with
>   ENOENT. I think the most likely failures are...
>   --> Either the name cache in the client is broken and has a hit
>   OR
>   --> The server replies NFS_OK for the lookup, even though it should have been removed.

The server replied ESTALE for the 'rm bar'.  Is that the lookup you mean?  I
don't think a lookup happened for /nfs/foo after the 'rm -r' completed, since
it was already the current directory (despite no longer existing).

> Did you try:
> sysctl debug.disable_vnfullpath=1 (or something close to disable_vnfullpath)
> to see if it helped?

If you mean debug.disablefullpath=1, yes, I tried that.  I also tried setting
vfs.lookup_shared=0; also no change.

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01000158fc3d9bab-65b7741f-ca02-4024-a34c-b8be22a3b5e6-000000>