From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: Re: Does NFS4 need st_gen?
Date: Thu, 20 Oct 2011 08:02:07 -0400 [thread overview]
Message-ID: <20111020120207.GL5444@fieldses.org> (raw)
In-Reply-To: <87d3dsdcf4.fsf@inspiron.ap.columbia.edu>
On Wed, Oct 19, 2011 at 03:11:27PM -0400, Nikolaus Rath wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
> > On Wed, Oct 19, 2011 at 10:17:43AM -0400, Nikolaus Rath wrote:
> >> Does NFS4 still depend on inode generation numbers? I understand that
> >> earlier NFS versions used file handles based on inode and generation
> >> number, but it seems to me that this shouldn't be required anymore with
> >> the (stateful) NFS4.
> >
> > Yes, it's true that NFSv4 has open and close operations, but filehandles
> > are still used a great deal outside of that, and clients are still
> > allowed to assume that the same filehandle always refers to the same
> > object.
> >
> > http://www.ietf.org/rfc/rfc3530.txt, section 4.2.1:
> >
> > "If two filehandles from the same server are equal, they MUST
> > refer to the same file."
>
> Duh - that's a disappointment. Thanks for the pointer!
Just curious--why do you care?
--b.
next prev parent reply other threads:[~2011-10-20 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:17 Does NFS4 need st_gen? Nikolaus Rath
2011-10-19 17:15 ` J. Bruce Fields
2011-10-19 19:11 ` Nikolaus Rath
2011-10-20 12:02 ` J. Bruce Fields [this message]
2011-10-20 17:21 ` Nikolaus Rath
2011-10-20 19:57 ` J. Bruce Fields
2011-10-20 20:37 ` Nikolaus Rath
2011-10-21 0:07 ` Trond Myklebust
2011-10-21 13:54 ` Nikolaus Rath
2011-10-21 16:00 ` Trond Myklebust
2011-10-21 16:09 ` Nikolaus Rath
2011-10-21 17:10 ` Trond Myklebust
2011-10-21 17:44 ` Nikolaus Rath
2011-10-22 18:47 ` Boaz Harrosh
2011-10-22 18:59 ` Boaz Harrosh
2011-10-22 20:10 ` Nikolaus Rath
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=20111020120207.GL5444@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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