From: Bernardo Innocenti <bernie@develer.com>
To: Bernardo Innocenti <bernie@develer.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
lkml <linux-kernel@vger.kernel.org>,
Neil Conway <nconway_kernel@yahoo.co.uk>,
nfs@lists.sourceforge.net
Subject: Re: NFS client bug in 2.6.8-2.6.11
Date: Tue, 08 Mar 2005 08:03:54 +0100 [thread overview]
Message-ID: <422D4E5A.1050409@develer.com> (raw)
In-Reply-To: <422D485F.5060709@develer.com>
Bernardo Innocenti wrote:
> Trond Myklebust wrote:
>
> I also can't reproduce the problem on an older
> client running 2.4.21.
Well, actually I tried harder with the 2.4.21
client and I obtained a similar effect:
naraku:/pub/linux/distro/fedora-devel# ll
ls: .: Stale NFS file handle
naraku:/pub/linux/distro/fedora-devel# cd -
/arc/linux
naraku:/arc/linux# cd -
/pub/linux/distro/fedora-devel
naraku:/pub/linux/distro/fedora-devel# ll
... (lots of files)
So, instead of ENOENT I get ESTALE on 2.4.21.
May well be a server bug then. The server is running
2.6.10-1.766_FC3. Do you think I should try installing
a vanilla kernel on the server?
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2005-03-08 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 4:53 NFS client bug in 2.6.8-2.6.11 Bernardo Innocenti
2005-03-08 5:30 ` Trond Myklebust
2005-03-08 5:30 ` Trond Myklebust
2005-03-08 6:38 ` Bernardo Innocenti
2005-03-08 6:47 ` Trond Myklebust
2005-03-08 6:47 ` Trond Myklebust
2005-03-08 9:26 ` Bernardo Innocenti
2005-03-08 7:03 ` Bernardo Innocenti [this message]
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=422D4E5A.1050409@develer.com \
--to=bernie@develer.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nconway_kernel@yahoo.co.uk \
--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 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.