From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: [PATCH] cifs: Allow nfsd over cifs Date: Tue, 1 Mar 2011 15:34:45 -0500 Message-ID: <20110301203445.GE20599@fieldses.org> References: <20110228234225.GC14237@fieldses.org> <20110228235910.GD14237@fieldses.org> <20110301032808.GA17725@fieldses.org> <20110301180700.GC20599@fieldses.org> <20110301192102.GD20599@fieldses.org> <20110301150949.6ca5b880@tlielax.poochiereds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeff Layton , Shirish Pargaonkar , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve French Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: On Tue, Mar 01, 2011 at 02:11:32PM -0600, Steve French wrote: > I vaguely remember that the same problem can occur with nfsd on a > local file system Not true; as I've said, exportable local filesystems know how to look up a file on disk by filehandle. > and that nfs clients have to be able to recover from > ESTALE (e.g. lookup/delete/create/lookup would fail with ESTALE > otherwise). It is true, however, that there are some *other* cases when a server can return ESTALE. In those cases (such as the one Peter Staubach discusses in more detail at http://lwn.net/Articles/272684/) there may be some recovery that a client might reasonably attempt. Alas, no client can be expected to recover from ESTALE errors on an opened file--those will just be passed on to the application. --b.