From: Bernardo Innocenti <bernie@develer.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Neil Conway <nconway_kernel@yahoo.co.uk>, nfs@lists.sourceforge.net
Subject: NFS client bug in 2.6.8-2.6.11
Date: Tue, 08 Mar 2005 05:53:50 +0100 [thread overview]
Message-ID: <422D2FDE.2090104@develer.com> (raw)
Hello,
This problem was previously described by Neil Conway.
All relevant information here:
http://lkml.org/lkml/2005/2/10/97
I still see this very same problem on 2.6.11 vanilla and in
Fedora/RawHide hernels. It has haunted me for a couple of
months on several Fedora clients. Strangely, a Gentoo
client isn't affected, but I couldn't investigate further.
When the current directory becomes inaccessible, it remains
so until I cd somewhere else and then cd back to it.
Sometimes I must wait a few seconds before cd succeeds.
Here's a sample session:
[executing a find / in another shell to trigger the bug]
beetle:/pub/linux/distro/fedora-devel# ll
ls: .: No such file or directory
beetle:/pub/linux/distro/fedora-devel# cd -
/
beetle:/# cd -
bash: cd: /pub/linux/distro/fedora-devel: No such file or directory
beetle:/#
[...a few seconds later...]
beetle:/# cd -
/pub/linux/distro/fedora-devel
Appears to be a client bug. The problem only happens
when there's heavy filesystem activity on other
filesystems (local or NFS).
NFS mount options: rw,_netdev,rsize=32768,wsize=32768,hard,intr,proto=udp,addr=10.3.3.1
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next reply other threads:[~2005-03-08 4:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 4:53 Bernardo Innocenti [this message]
2005-03-08 5:30 ` NFS client bug in 2.6.8-2.6.11 Trond Myklebust
2005-03-08 6:38 ` Bernardo Innocenti
2005-03-08 6:47 ` Trond Myklebust
2005-03-08 9:26 ` Bernardo Innocenti
2005-03-08 7:03 ` Bernardo Innocenti
2005-03-08 8:56 ` Anders Saaby
2005-03-08 22:25 ` Bernardo Innocenti
-- strict thread matches above, loose matches on Subject: below --
2005-03-15 23:44 Neil Conway
2005-03-16 2:49 ` Bernardo Innocenti
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=422D2FDE.2090104@develer.com \
--to=bernie@develer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
--cc=nfs@lists.sourceforge.net \
/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