[NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19

[NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19

[Yusuf Goolamabbas]

Anybody know if this is bug is fixed and if so in which kernel revision.
Any ideas about its impact on vendor kernels (RHEL/SUSE Enterprise)

http://opensrs.com/blog/2008/10/technical-debrief-on-october-cluster-a-email-service-issue/

Regards, Yusuf

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
    http://vger.kernel.org/vger-lists.html#linux-nfs

Re: [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19

[Jeff Layton]

On Sun, 19 Oct 2008 11:28:11 +0800
Yusuf Goolamabbas <yusufg-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org> wrote:

> Anybody know if this is bug is fixed and if so in which kernel revision.
> Any ideas about its impact on vendor kernels (RHEL/SUSE Enterprise)
> 
> http://opensrs.com/blog/2008/10/technical-debrief-on-october-cluster-a-email-service-issue/
> 

I know that more recent RHEL kernels have this fixed. The bug to track it was here:

https://bugzilla.redhat.com/show_bug.cgi?id=369561

It's also easy to tell if you have a kernel with this problem. Just do
a single TCP mount on the client, and then run:

$ rpcinfo -p

...you should see port registrations for nlockmgr. If you don't see any
UDP ones, then the kernel has the problem.

-- 
Jeff Layton <jlayton@redhat.com>

Re: [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19

[Trond Myklebust]

On Sun, 2008-10-19 at 06:44 -0400, Jeff Layton wrote:
> On Sun, 19 Oct 2008 11:28:11 +0800
> Yusuf Goolamabbas <yusufg-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org> wrote:
> 
> > Anybody know if this is bug is fixed and if so in which kernel revision.
> > Any ideas about its impact on vendor kernels (RHEL/SUSE Enterprise)
> > 
> > http://opensrs.com/blog/2008/10/technical-debrief-on-october-cluster-a-email-service-issue/
> > 
> 
> I know that more recent RHEL kernels have this fixed. The bug to track it was here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=369561
> 
> It's also easy to tell if you have a kernel with this problem. Just do
> a single TCP mount on the client, and then run:
> 
> $ rpcinfo -p
> 
> ...you should see port registrations for nlockmgr. If you don't see any
> UDP ones, then the kernel has the problem.
> 

Note that the workaround was simply to add 

     lockd.nlm_udpport=<unused portnumber>

to your kernel bootparameters.

Cheers
  Trond