Re: NFS4 crack

[Christoph Hellwig <hch@infradead.org>]

On Mon, Sep 19, 2005 at 02:53:36PM -0400, William A.(Andy) Adamson wrote:
> > They are not nice, but quite a bit different, as we are trying to execute
> > them, which can't have bad side-effects in case they don't exist.
> > 
> > What nfsd does is expecting a directory to be present on which it can
> > do various operations.  That's much worse then trying to execute or 
> > even read from a file.
> 
> what we could do is not provide a default, and turn off reboot recovery (no 
> grace period) if the recovery directory is not configured.
>
> > Besides that all this directory handling really
> > belongs into userland as pointed out _three times_ now.
> 
> We were anticipating placing data into files in the recovery directory at each 
> OPEN and each LOCK call in order to limit the scope of the NFSv4 grace period 
> to the state that was actually in use prior to the reboot. We therefore went 
> ahead with a kernel implementation for performance reasons.

Then pass in a file descriptor for the each client.  Doing all this
directory operations is not an option - if you need to do actual file I/O
to them that's less of an problem.

And please discuss such design issues here on -fsdevel.