Date: Mon, 12 Dec 2016 06:15:14 +0000 From: Colin Percival <cperciva@tarsnap.com> To: 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: <01000158f1abbd72-01e38784-8ba0-4c71-9689-76dac8fece0a-000000@email.amazonses.com> In-Reply-To: <20161212054233.GU8460@kduck.kaduk.org> References: <01000158f023675b-41b35a73-4428-4937-853b-62db4fb9b984-000000@email.amazonses.com> <20161212054233.GU8460@kduck.kaduk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/11/16 21:42, Benjamin Kaduk 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 >> >> Then the final 'rm bar' fails with 'Stale NFS file handle'. > > Amusingly, this just came up recently: > > https://www.ietf.org/mail-archive/web/nfsv4/current/msg15115.html (et seq) > > But I guess you did not specify which version of the NFS protocol you were > using... I'm using NFSv4.1, but this isn't quite the same... that link refers to having one NFS client remove a file out from underneath a different client, while I'm talking about having an NFS client remove a file from underneath *itself*. -- 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?01000158f1abbd72-01e38784-8ba0-4c71-9689-76dac8fece0a-000000>