From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Junfeng Yang <yjf@stanford.edu>,
nfs@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ext2-devel@lists.sourceforge.net, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] inconsistent NFS stat cache (NFS on ext3, 2.6.11)
Date: Sun, 13 Mar 2005 15:42:29 -0500 [thread overview]
Message-ID: <1110746550.23876.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20050313200412.GA21521@nevyn.them.org>
su den 13.03.2005 Klokka 15:04 (-0500) skreiv Daniel Jacobowitz:
> I can't find any documentation about this, but it seems like the same
> problem that has been causing me headaches lately; when I replace glibc
> from the server side of an nfsroot, the client has a couple of
> variously wrong reads before it sees the new files. If it breaks NFS
> so badly, why is it the default for the Linux NFS server?
No, that's a very different issue: you are violating the NFS cache
consistency rules if you are changing a file that is being held open by
other machines.
The correct way to do the above is to use GNU install with the '-b'
option: that will rename the version of glibc that is in use, and then
install the new glibc in a different inode.
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
next prev parent reply other threads:[~2005-03-13 20:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 11:56 Junfeng Yang
2005-03-13 5:04 ` Trond Myklebust
2005-03-13 6:16 ` Junfeng Yang
2005-03-13 20:04 ` Daniel Jacobowitz
2005-03-13 20:42 ` Trond Myklebust [this message]
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
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=1110746550.23876.8.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=dan@debian.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
--cc=nfs@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®