All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <righiandr@users.sourceforge.net>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: Neil Brown <neilb@suse.de>, nfs@lists.sourceforge.net
Subject: Re: nfsd closes port 2049
Date: Tue, 16 Oct 2007 19:50:19 +0200 (MEST)	[thread overview]
Message-ID: <4714F9DA.8070407@users.sourceforge.net> (raw)
In-Reply-To: <EXNANE014r3mbfJ8VrR0000070e@exnane01.hq.netapp.com>

Talpey, Thomas wrote:
> At 05:57 PM 10/15/2007, Andrea Righi wrote:
>> Neil Brown wrote:
>>>> 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.
> 
> BTW, the nfsd_acceptable() issue is different from this one, and the
> no_subtree_check I suggested may still be needed (right Neil?). I'm
> interested in what you find - keep us posted.
> 
> Tom.
> 

I've just finished to update the kernel to 2.6.16.53-0.8-smp (always SLES10
x86_64 of course) that includes the fix reported by Neil. I've exported the fs
withtout the no_subtree_check option for now, let's see in these days what'll
happen.

-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

  reply	other threads:[~2007-10-16 17:50 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
2007-10-15 21:57     ` [NFS] " Andrea Righi
2007-10-16 12:10     ` Talpey, Thomas
2007-10-16 17:50       ` Andrea Righi [this message]
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=4714F9DA.8070407@users.sourceforge.net \
    --to=righiandr@users.sourceforge.net \
    --cc=Thomas.Talpey@netapp.com \
    --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.