From: Willy Tarreau <willy@w.ods.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Leif Nixon <nixon@nsc.liu.se>, linux-kernel@vger.kernel.org
Subject: Re: Cache invalidation bug in NFS v3 - trivially reproducible
Date: Wed, 12 Oct 2005 06:31:08 +0200 [thread overview]
Message-ID: <20051012043108.GI22601@alpha.home.local> (raw)
In-Reply-To: <1129042077.11164.9.camel@lade.trondhjem.org>
Hi,
On Tue, Oct 11, 2005 at 10:47:57AM -0400, Trond Myklebust wrote:
> ty den 11.10.2005 Klokka 11:09 (+0200) skreiv Leif Nixon:
> > Hi,
> >
> > We have come across a bug where a NFS v3 client fails to invalidate
> > its data cache for a file even though it realizes that the file
> > attributes have changed. We have been able to recreate the bug on a
> > range of kernel versions and different underlying file systems.
> >
> > Here's a minimal way to reproduce the error (there seems to be some
> > timing issues involved, but this has worked at least 90% of the time):
> >
> > NFS client n1 NFS client n2
> >
> > $ echo 1 > f
> > $ cat f
> > 1
> > $ touch .
> > $ echo 2 > f
> > $ touch f
> > $ cat f
> > 1
> >
> > Now client n2 is stuck in a state where it uses its old cached data
> > forever (or at least for several hours):
>
> Yep. I can see a problem whereby the cache is "losing" consistency
> information when you do this sort of thing. I'm working on a fix.
Trond, if this can help you, I *cannot* reproduce this with 2.4 clients
and server.
Cheers,
Willy
next prev parent reply other threads:[~2005-10-12 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 9:09 Leif Nixon
2005-10-11 9:22 ` Jakob Oestergaard
2005-10-11 14:47 ` Trond Myklebust
2005-10-12 4:31 ` Willy Tarreau [this message]
2005-10-13 22:34 ` Trond Myklebust
2005-10-14 13:34 ` Leif Nixon
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=20051012043108.GI22601@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nixon@nsc.liu.se \
--cc=trond.myklebust@fys.uio.no \
/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
Powered by JetHome