From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: protocol question
Date: Wed, 26 Jul 2006 08:24:10 -0400
Message-ID: <1153916650.5656.27.camel@localhost>
References: <200607261247.35653.bernd.schubert@pci.uni-heidelberg.de>
	<1153914204.5656.13.camel@localhost>
	<200607261356.38520.bernd.schubert@pci.uni-heidelberg.de>
	<1153916394.5656.23.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: bernd-schubert@gmx.de
In-Reply-To: <1153916394.5656.23.camel@localhost>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Wed, 2006-07-26 at 08:20 -0400, Trond Myklebust wrote:
> 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.

Cheers,
  Trond


-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs