From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: bernd-schubert@gmx.de
Cc: nfs@lists.sourceforge.net
Subject: Re: protocol question
Date: Wed, 26 Jul 2006 08:24:10 -0400 [thread overview]
Message-ID: <1153916650.5656.27.camel@localhost> (raw)
In-Reply-To: <1153916394.5656.23.camel@localhost>
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
next prev parent reply other threads:[~2006-07-28 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 10:47 (no subject) Bernd Schubert
2006-07-26 11:43 ` Trond Myklebust
2006-07-26 11:56 ` protocol question Bernd Schubert
2006-07-26 12:19 ` Trond Myklebust
2006-07-26 12:24 ` Trond Myklebust [this message]
2006-07-26 15:32 ` Bernd Schubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1153916650.5656.27.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=bernd-schubert@gmx.de \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).