From: Daniel Jacobowitz <dan@debian.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Junfeng Yang <yjf@stanford.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [CHECKER] inconsistent NFS stat cache (NFS on ext3, 2.6.11)
Date: Sun, 13 Mar 2005 19:54:13 -0500 [thread overview]
Message-ID: <20050314005413.GA17711@nevyn.them.org> (raw)
In-Reply-To: <1110761410.30085.13.camel@lade.trondhjem.org>
On Sun, Mar 13, 2005 at 07:50:09PM -0500, Trond Myklebust wrote:
> Sorry, but you should _never_ have gotten an ESTALE error if the file
> was not in use when you deleted the old copy of glibc. A fresh call to
> open() will always result in a new lookup of the filehandle.
> What may have happened in the case of the EIO error is that you may have
> raced: i.e. a client starts reading the file while it is being copied
> to.
It is in a separate root filesystem, currently not used by anything on
the target. It is likely to be in cache, but I can absolutely
guarantee it isn't open. Hmm, server is x86_64 2.6.7, client is 2.6.10
MIPS. I should upgrade them and see if that helps.
Unfortunately I haven't found any smaller testcases than installing an
entire root FS.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-14 0:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 11:56 [CHECKER] inconsistent NFS stat cache (NFS on ext3, 2.6.11) Junfeng Yang
2005-03-12 11:56 ` Junfeng Yang
2005-03-13 5:04 ` Trond Myklebust
2005-03-13 5:04 ` Trond Myklebust
2005-03-13 6:16 ` Junfeng Yang
2005-03-13 6:16 ` Junfeng Yang
2005-03-13 7:04 ` Junfeng Yang
2005-03-13 15:18 ` Trond Myklebust
2005-03-13 20:04 ` Daniel Jacobowitz
2005-03-13 20:04 ` Daniel Jacobowitz
2005-03-13 20:42 ` Trond Myklebust
2005-03-13 20:42 ` Trond Myklebust
2005-03-13 20:46 ` Trond Myklebust
2005-03-13 20:46 ` Trond Myklebust
2005-03-14 0:35 ` Daniel Jacobowitz
2005-03-14 0:50 ` Trond Myklebust
2005-03-14 0:54 ` Daniel Jacobowitz [this message]
2005-03-14 0:56 ` Neil Brown
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=20050314005413.GA17711@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=yjf@stanford.edu \
/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.