Re: protocol question

[Bernd Schubert <bernd.schubert@pci.uni-heidelberg.de>]

> > But the client returns an i/o error to the userspace, is this correct?
>
> No. It will return an ESTALE to userspace in this case.

Sorry, I didn't express myself properly, it _did_ return i/o error.

[...]
> Right. The inode generation number changes when the inode number is
> reused. After that, any NFS rpc request containing the filehandle with
> the old generation number should receive an immediate NFSERR3_STALE.

> Oops. Actually, it would be more correct to say that the filehandle is
> invalidated immediately once the file has been deleted on the server.
>
> The generation number is there in order to ensure that the old
> filehandle is not 'resurrected' when the inode number is reused.

I need to have a look how Pascal actually used the generation numbers.

>
> My point about inotify was merely a way to help enforce that in the case
> where a userland-based server might want to cache filehandles. I've no
> idea whether or not unfs3 actually does that sort of thing.

There is a cache, but thats the part I so far never looked into.

Thanks a lot for your help,
	Bernd

-- =

Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universit=E4t Heidelberg
INF 229
69120 Heidelberg
e-mail: bernd.schubert@pci.uni-heidelberg.de

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs