Linux NFS development
 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: Thu, 18 Oct 2007 14:42:35 +0200 (MEST)	[thread overview]
Message-ID: <471754BA.7000907@users.sourceforge.net> (raw)
In-Reply-To: <EXNANE013MBhe3WYIgo0000075b@exnane01.hq.netapp.com>

Talpey, Thomas wrote:
> At 02:30 AM 10/18/2007, Neil Brown wrote:
>> On Tuesday October 16, Thomas.Talpey@netapp.com wrote:
>>> 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.
>> I don't know exactly what you mean by "the nfsd_acceptable() issue",
>> but whatever it is, it would be completely separate from tcp
>> connections.
> 
> It was the messages in the logs Andrea sent, here's one:
> 
>>> Oct 13 05:20:56 node0101 kernel: nfsd_acceptable failed at ffff8100c7873700
> 
>> If a filesystems got unexported, or a "chmod -x" made some directories
>> unaccessible, it would not close any TCP connection.  It would simply
>> return an error status for every request, leaving the TCP connection
>> active.
> 
> Fair enough - the clients wouldn't automatically close the connections
> due to this, either. So the race condition at the server is the probable
> cause of Andrea's observed error.
> 
> I still think adding no_subtree_check will help the situation. These
> export failures are coming from some failed check at the server, and
> they're rare enough to make me think there's a GPFS or other server
> issue at work from time to time. 

The NFS server is working fine for the 2nd day using the fix (with kernel
2.6.16.53-0.8-smp), but I'm not yet using the no_subtree_check option. I tried
to stress the filesystem with multiple accesses from all the clients (256),
alterning with periods of inactivity. This was a good "pattern" to reproduce the
problem and since it didn't happen anymore I'm considering the issue resolved.

Anyway, I'm quite lucky :-) and I've another cluster with another identical NFS
server: same hardware, same distro, same number of clients, etc, so I can try
the no_subtree_check there.

-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-18 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 16:57 nfsd closes port 2049 Andrea Righi
2007-10-15 18:04 ` Talpey, Thomas
2007-10-15 18:23   ` 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-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 [this message]
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=471754BA.7000907@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox