Re: nfsv3 client process stuck in rwsem_down_failed_common()

[Frank van Maarseveen <frankvm@frankvm.com>]

On Mon, May 14, 2007 at 07:02:16PM +0200, Frank van Maarseveen wrote:
> 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

hmm, so the timeout has become 10 * HZ * HZ?


-- 
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