From: Stephan Koledin <skoledin@neolinear.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS lockups with 2.4.18
Date: Fri, 26 Sep 2003 11:47:49 -0400 [thread overview]
Message-ID: <3F745FA5.5010907@neolinear.com> (raw)
In-Reply-To: <3F7347FF.2000403@neolinear.com>
Some more observations on this issue...
I've noticed that lockd appears to be the culprit. It is the first
process to get stuck in a 'D' state. Eventually, all the nfsd processes
follow it, apparently one at a time.
I think I've narrowed the cause down to some questionable SETLK calls
from Solaris 8 clients. The suspect 3rd party app is a bit complex,
however, so still trying to isolate the exact triggering sequence of events.
In the process of trying to dig up some clues, I ran into a similar
problem reported on the lkml (http://lkml.org/lkml/2003/1/29/59). From
private correspondence with the submitter, he is still encountering
problems, and continues to experiment with the 2.4.2x series and NFS
patches in hope of relief. It may not be the exact same problem, but it
is very similar.
If anyone has any ideas about this problem, please let me know. I
certainly don't mind trying a more recent kernel, but hate to just dive
in blindly hoping for a fix that may not be there... Any debugging
suggestions?
Thanks.
-Stephan
--
Stephan B Koledin
Network Systems Developer
http://neolinear.com/
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-26 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 16:51 NFS lockups with 2.4.18 Stephan Koledin
2003-09-25 19:54 ` Stephan Koledin
2003-09-26 15:47 ` Stephan Koledin [this message]
2003-09-30 23:08 ` Stephan Koledin
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=3F745FA5.5010907@neolinear.com \
--to=skoledin@neolinear.com \
--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.