From: Timo Sirainen <tss@iki.fi>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Benny Halevy <bhalevy@panasas.com>,
Peter Staubach <staubach@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: inode caching
Date: Wed, 28 May 2008 18:20:57 +0300 [thread overview]
Message-ID: <1211988057.3904.304.camel@hurina> (raw)
In-Reply-To: <20080528135935.GA17606@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Wed, 2008-05-28 at 09:59 -0400, J. Bruce Fields wrote:
> On Wed, May 28, 2008 at 08:38:29AM +0300, Benny Halevy wrote:
> > On May. 27, 2008, 22:13 +0300, Timo Sirainen <tss@iki.fi> wrote:
> > > I'd still like to understand why exactly this happens though. Maybe
> > > there's a chance that this is just a bug in the current NFS
> > > implementation so I could keep using my current code (which is
> > > actually very difficult to break even with stress testing, so if this
> > > doesn't get fixed on kernel side I'll probably just leave my code as
> > > it is). I guess I'll start debugging the NFS code to find out what's
> > > really going on.
> >
> > My guess would be that the new incarnation of the inode generates the
> > same filehandle as the old one, not just the same inode number.
>
> That sounds like a server bug (either in the server itself, or the
> filesystem it's exporting); the generation number is supposed to prevent
> this.
And if it happens, wouldn't the struct inode on NFS client be the same
for both files then? I'm seeing different results for fstat() calls
(just with the same st_ino).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-05-28 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 20:58 inode caching Timo Sirainen
2008-05-27 12:48 ` Peter Staubach
2008-05-27 15:40 ` Timo Sirainen
2008-05-27 18:09 ` Peter Staubach
2008-05-27 19:13 ` Timo Sirainen
2008-05-28 5:38 ` Benny Halevy
2008-05-28 13:59 ` J. Bruce Fields
2008-05-28 15:20 ` Timo Sirainen [this message]
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=1211988057.3904.304.camel@hurina \
--to=tss@iki.fi \
--cc=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=staubach@redhat.com \
/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