SCIENTIFIC-LINUX-USERS Archives

August 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dr Andrew C Aitchison <[log in to unmask]>
Reply To:
Dr Andrew C Aitchison <[log in to unmask]>
Date:
Fri, 29 Aug 2008 10:02:41 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (41 lines)
On Fri, 29 Aug 2008, Faye Gibbins wrote:

> We're running SL5 with this kernel:
>
> 2.6.18-92.1.10.el5 x86_64
>
> We're experiencing regular lockd failures on one of our nfs servers.
>
> One other with doesn't have the problem is still running 2.6.18-53.1.14.el5
>
> The problem is diagnosed by running:
>
> time flock ~/junk echo ok; rm ~/junk
>
> on an affected client of the server.
>
> It may be related to this report of a simular bug in the kernel discused 
> here:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/181996
>
> Does anyone know if the latest SL5 kernels are affected with this bug? Can 
> something be done as the only fix we can find is to restart the box the NFS 
> server lives on.

This sounds like
https://bugzilla.redhat.com/show_bug.cgi?id=453094

I believe that 2.6.18-92.1.10.el5 x86_64 *is* the latest version
both of EL5 and SL5.

The RedHat bug report links to binaries which seem to fix it,
but they don't seem to be prepared to release them officially
until 5.3.
Since they did the same thing with another NFS bug in 5.1
I have come to the conclusion that NFS is not important to RedHat.

-- 
Dr. Andrew C. Aitchison		Computer Officer, DPMMS, Cambridge
[log in to unmask]	http://www.dpmms.cam.ac.uk/~werdna

ATOM RSS1 RSS2