From: Bernardo Innocenti <bernie@develer.com>
To: Anders Saaby <as@cohaesio.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 23:25:07 +0100 [thread overview]
Message-ID: <422E2643.4010004@develer.com> (raw)
In-Reply-To: <200503080956.41086.as@cohaesio.com>
Anders Saaby wrote:
> On Tuesday 08 March 2005 08:03, Bernardo Innocenti wrote:
>
>>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:
>>
>>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?
>
>
> We have seen lots of ESTALE's/ENOENT's when the server is running 2.6.10
> (vanilla). Don't know if this was supposed to be fixed in the 2.6.10-FC
> kernels, but vanilla 2.6.11 doesen't seem to have this bug at all.
>
> You mention a lot of kernel versions including 2.6.11, and I can't really
> figure out whether you are talking abount the clients or the server. -
> Anyways if your server has only run with 2.6.10 - try 2.6.11.
Thank you, I've finally nailed it down by upgrading the
*server* kernel from 2.6.10-1.770_FC3 to 2.6.10-1.770_FC3.
The latter is basically 2.6.10-ac12 plus a bunch of vendor
specific patches.
> - Apologies if I missed something obvious.
No, *I* did. All the clues I had leaded me to the client
side, while the problem was in the server instead.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2005-03-08 22:25 UTC|newest]
Thread overview: 10+ 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 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 [this message]
-- 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=422E2643.4010004@develer.com \
--to=bernie@develer.com \
--cc=as@cohaesio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox