From: Jeff Garzik <jgarzik@pobox.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS cache consistancy appears to be broken...
Date: Tue, 29 Nov 2005 21:38:02 -0500 [thread overview]
Message-ID: <438D108A.6020709@pobox.com> (raw)
In-Reply-To: <438D0E80.2020905@RedHat.com>
Steve Dickson wrote:
> Hey Trond,
>
> The attached patch seems to break cache consistence in a big way....
> Doing the following:
> 1. On server:
> $ mkdir ~/t
> $ echo Hello > ~/t/tmp
>
> 2. On client, wait for a string to appear in this file:
> $ until grep -q foo t/tmp ; do echo -n . ; sleep 1 ; done
>
> 3. On server, create a *new* file with the same name containing that
> string:
> $ mv ~/t/tmp ~/t/tmp.old; echo foo > ~/t/tmp
>
> will shows how the client will never (and I mean never ;-) ) see
> the updated file. I reverted this patch and everything started
> work as expected... so it appears using a jiffy-based cache
> verifiers may not be such a good idea....
>
> Note: I am using 2.6.15-rc2 kernel.
Very interesting. This sounds similar to the problem I reported a week
or so ago. The circumstances were too unique to easily reproduce.
Jeff
next prev parent reply other threads:[~2005-11-30 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200510281607.j9SG7Tll024133@hera.kernel.org>
2005-11-30 2:29 ` NFS cache consistancy appears to be broken Steve Dickson
2005-11-30 2:38 ` Jeff Garzik [this message]
2005-11-30 7:10 ` Trond Myklebust
2005-11-30 14:25 ` Steve Dickson
2005-11-30 14:47 ` Trond Myklebust
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=438D108A.6020709@pobox.com \
--to=jgarzik@pobox.com \
--cc=SteveD@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--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