From: Bernardo Innocenti Subject: Re: NFS client bug in 2.6.8-2.6.11 Date: Tue, 08 Mar 2005 23:25:07 +0100 Message-ID: <422E2643.4010004@develer.com> References: <422D2FDE.2090104@develer.com> <422D485F.5060709@develer.com> <422D4E5A.1050409@develer.com> <200503080956.41086.as@cohaesio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Trond Myklebust , lkml , Neil Conway , nfs@lists.sourceforge.net To: Anders Saaby In-Reply-To: <200503080956.41086.as@cohaesio.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: 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/