From: Frank van Maarseveen <frankvm@frankvm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux NFS mailing list <nfs@lists.sourceforge.net>,
Frank van Maarseveen <frankvm@frankvm.com>
Subject: Re: nfsv3 client process stuck in rwsem_down_failed_common()
Date: Mon, 14 May 2007 19:02:16 +0200 [thread overview]
Message-ID: <20070514170216.GA6475@janus> (raw)
In-Reply-To: <1179161763.6474.31.camel@heimdal.trondhjem.org>
On Mon, May 14, 2007 at 12:56:03PM -0400, Trond Myklebust wrote:
> On Mon, 2007-05-14 at 18:39 +0200, Frank van Maarseveen wrote:
> > On Mon, May 14, 2007 at 12:32:59PM -0400, Trond Myklebust wrote:
> > > On Mon, 2007-05-14 at 18:15 +0200, Frank van Maarseveen wrote:
> > > > > Could you please use 'echo 0 >/proc/sys/sunrpc/rpc_debug' in order to
> > > > > find out on which rpc queue these tasks are sleeping?
> > > >
> > > > -pid- proc flgs status -client- -prog- --rqstp- -timeout -rpcwait -action- ---ops--
> > > > 30871 0002 0480 0 c7708614 100021 f43f4000 10000000 xprt_pending c050e4d0 c057f3f4
> > > > 30873 0002 0480 0 f00b4eb4 100021 cc809000 10000000 xprt_pending c050e4d0 c057f3f4
> > > ^^^^^^^^ Ouch!
> > >
> > > That is a pretty massive timeout. What is your value
> > > of /proc/sys/fs/nfs/nlm_timeout ?
> >
> > Unfortunately it became necessary to reboot the machine :-(. Right now it says 10.
>
> 10 seconds looks like the correct default. I assume that you hadn't
> changed that value prior to the reboot...
right, I didn't knew it existed and I'm not aware of any command which
can change it. Did some grepping around and it didn't turn up anything.
>
> One last question, just in case: what value are you using for CONFIG_HZ?
1000
--
Frank
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-14 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:54 nfsv3 client process stuck in rwsem_down_failed_common() Frank van Maarseveen
2007-05-14 15:59 ` Trond Myklebust
2007-05-14 16:05 ` Frank van Maarseveen
2007-05-14 16:11 ` Trond Myklebust
2007-05-14 16:15 ` Frank van Maarseveen
2007-05-14 16:32 ` Trond Myklebust
2007-05-14 16:39 ` Frank van Maarseveen
2007-05-14 16:56 ` Trond Myklebust
2007-05-14 17:02 ` Frank van Maarseveen [this message]
2007-05-14 17:05 ` Frank van Maarseveen
2007-05-14 17:15 ` Trond Myklebust
2007-05-14 17:17 ` Trond Myklebust
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=20070514170216.GA6475@janus \
--to=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.