From: Andrea Righi <righiandr@users.sourceforge.net>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: nfsd closes port 2049
Date: Mon, 15 Oct 2007 23:57:47 +0200 (MEST) [thread overview]
Message-ID: <4713E25D.6090302@users.sourceforge.net> (raw)
In-Reply-To: <18195.52347.544844.155538@notabene.brown>
Neil Brown wrote:
> On Monday October 15, a.righi@cineca.it wrote:
>> Hi all,
>>
>> I'm trying to debug a weird problem with nfsd on a 2.6.16.27-0.6-smp
>> kernel.
>>
>> 1 server: SuSE SLES 10 x86_64, config attached
>> 256 clients: RHEL4 Update 4 2.6.9-42.ELsmp x86_64
>>
>> Using nfs v3.
>>
>> The clients have been happily talking to the server for several days
>> without incident.
>>
>> The weird thing is that at a certain point the socket opened on port
>> 2049 on the NFS server is being closed for unknown reasons (or better
>> for unknown reasons for me!).
>
> This is fixed in any release based on 2.6.16.31 or later.
> The relevant mainline patch is
> 1a047060a99f274a7c52cfea8159e4142a14b8a7
> as below.
> So update your kernel package.
Thanks Neil, looking at the source and in my logs this seems to explain
perfectly my problem. I'll try the patch ASAP.
-Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Righi <righiandr@users.sourceforge.net>
To: Neil Brown <neilb@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>, nfs@lists.sourceforge.net
Subject: Re: [NFS] nfsd closes port 2049
Date: Mon, 15 Oct 2007 23:57:47 +0200 (MEST) [thread overview]
Message-ID: <4713E25D.6090302@users.sourceforge.net> (raw)
In-Reply-To: <18195.52347.544844.155538@notabene.brown>
Neil Brown wrote:
> On Monday October 15, a.righi@cineca.it wrote:
>> Hi all,
>>
>> I'm trying to debug a weird problem with nfsd on a 2.6.16.27-0.6-smp
>> kernel.
>>
>> 1 server: SuSE SLES 10 x86_64, config attached
>> 256 clients: RHEL4 Update 4 2.6.9-42.ELsmp x86_64
>>
>> Using nfs v3.
>>
>> The clients have been happily talking to the server for several days
>> without incident.
>>
>> The weird thing is that at a certain point the socket opened on port
>> 2049 on the NFS server is being closed for unknown reasons (or better
>> for unknown reasons for me!).
>
> This is fixed in any release based on 2.6.16.31 or later.
> The relevant mainline patch is
> 1a047060a99f274a7c52cfea8159e4142a14b8a7
> as below.
> So update your kernel package.
Thanks Neil, looking at the source and in my logs this seems to explain
perfectly my problem. I'll try the patch ASAP.
-Andrea
next prev parent reply other threads:[~2007-10-15 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 16:57 nfsd closes port 2049 Andrea Righi
2007-10-15 16:57 ` [NFS] " Andrea Righi
2007-10-15 18:04 ` Talpey, Thomas
2007-10-15 18:04 ` [NFS] " Talpey, Thomas
2007-10-15 18:23 ` Andrea Righi
2007-10-15 18:23 ` [NFS] " Andrea Righi
2007-10-15 18:40 ` Talpey, Thomas
2007-10-15 19:34 ` Andrea Righi
2007-10-15 20:24 ` [NFS] " Neil Brown
2007-10-15 21:57 ` Andrea Righi [this message]
2007-10-15 21:57 ` Andrea Righi
2007-10-16 12:10 ` Talpey, Thomas
2007-10-16 17:50 ` Andrea Righi
2007-10-18 6:30 ` Neil Brown
2007-10-18 11:59 ` Talpey, Thomas
2007-10-18 12:42 ` Andrea Righi
2007-10-18 13:44 ` Talpey, Thomas
2007-10-18 14:34 ` Andrea Righi
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=4713E25D.6090302@users.sourceforge.net \
--to=righiandr@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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.