From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: Yusuf Goolamabbas
<yusufg-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org>,
linux-nfs@vger.kernel.org
Subject: Re: [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19
Date: Sun, 19 Oct 2008 12:45:01 -0400 [thread overview]
Message-ID: <1224434701.9433.3.camel@localhost> (raw)
In-Reply-To: <20081019064405.0db1e004-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
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
prev parent reply other threads:[~2008-10-19 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 3:28 [NFS] OpenSRS blog post alludes to a Linux NFS bug in 2.6.19 Yusuf Goolamabbas
[not found] ` <20081019032811.GA30801-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org>
2008-10-19 10:44 ` Jeff Layton
[not found] ` <20081019064405.0db1e004-RtJpwOs3+0O+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2008-10-19 16:45 ` Trond Myklebust [this message]
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=1224434701.9433.3.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=yusufg-lA0CmJ9G6+FWk0Htik3J/w@public.gmane.org \
/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.