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 18:05:47 +0200 [thread overview]
Message-ID: <20070514160547.GB5169@janus> (raw)
In-Reply-To: <1179158385.6474.11.camel@heimdal.trondhjem.org>
On Mon, May 14, 2007 at 11:59:45AM -0400, Trond Myklebust wrote:
> On Mon, 2007-05-14 at 17:54 +0200, Frank van Maarseveen wrote:
> > On a 2.6.21.1 NFSv3 client box multiple processes got stuck with
> > this trace:
> >
> > [<c02926e5>] rwsem_down_failed_common+0x85/0x180
> > [<c052a36d>] rwsem_down_read_failed+0x1d/0x30
> > [<c052a437>] call_rwsem_down_read_failed+0x7/0x10
> > [<c022622e>] nlmclnt_unlock+0x2e/0xc0
> > [<c02258da>] nlmclnt_proc+0x29a/0x2d0
> > [<c01f088e>] nfs3_proc_lock+0xe/0x10
> > [<c01e3904>] do_unlk+0x44/0x70
> > [<c01e3a9d>] nfs_lock+0xbd/0x120
> > [<c017dfd1>] locks_remove_posix+0xb1/0xc0
> > [<c016dc8d>] filp_close+0x2d/0x70
> > [<c01248a6>] close_files+0x56/0x70
> > [<c012490c>] put_files_struct+0x1c/0x50
> > [<c012533a>] do_exit+0x13a/0x3f0
> > [<c0125649>] do_group_exit+0x29/0x70
> > [<c012e73f>] get_signal_to_deliver+0x21f/0x2b0
> > [<c0103e96>] do_signal+0x56/0x160
> > [<c0103fde>] do_notify_resume+0x3e/0x40
> > [<c01041ae>] work_notifysig+0x13/0x25
> >
> > Two processes had an independent shared read lock on different files
> > and when killing them with ^C they got stuck in state 'D' with above
> > stack trace. I'm not sure what brought then there other than that the
> > server went through a number of unusual reboots for testing purposes.
>
> Are there any processes with a name of the form '<hostname>-reclaim'
> hanging too?
yes, two of them, each for a different NFS server (as I would expect).
The traces are identical:
[<c0512f1d>] rpc_wait_bit_interruptible+0x1d/0x30
[<c0529114>] __wait_on_bit+0x44/0x70
[<c05291bd>] out_of_line_wait_on_bit+0x7d/0x90
[<c05137f5>] __rpc_execute+0xa5/0x1e0
[<c0513949>] rpc_execute+0x19/0x20
[<c050da56>] rpc_call_sync+0x96/0xa0
[<c0225b17>] nlmclnt_call+0x77/0x1e0
[<c02261ac>] nlmclnt_reclaim+0x6c/0xc0
[<c0225236>] reclaimer+0x106/0x1f0
[<c0105317>] kernel_thread_helper+0x7/0x10
--
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 16:05 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 [this message]
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
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=20070514160547.GB5169@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.