From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: nfsv3 client process stuck in rwsem_down_failed_common()
Date: Mon, 14 May 2007 17:54:49 +0200 [thread overview]
Message-ID: <20070514155449.GA5169@janus> (raw)
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.
--
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 reply other threads:[~2007-05-14 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 15:54 Frank van Maarseveen [this message]
2007-05-14 15:59 ` nfsv3 client process stuck in rwsem_down_failed_common() 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
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=20070514155449.GA5169@janus \
--to=frankvm@frankvm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox