From: "J. Bruce Fields" <bfields@fieldses.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Timo Sirainen <tss@iki.fi>, Peter Staubach <staubach@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: inode caching
Date: Wed, 28 May 2008 09:59:35 -0400 [thread overview]
Message-ID: <20080528135935.GA17606@fieldses.org> (raw)
In-Reply-To: <483CEFD5.8050507@panasas.com>
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.
--b.
next prev parent reply other threads:[~2008-05-28 14:00 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 [this message]
2008-05-28 15:20 ` Timo Sirainen
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=20080528135935.GA17606@fieldses.org \
--to=bfields@fieldses.org \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=staubach@redhat.com \
--cc=tss@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.