From: Frank van Maarseveen <frankvm@frankvm.com>
To: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: 3.1.4: NFSv3 RPC scheduling issue?
Date: Mon, 5 Dec 2011 17:50:21 +0100 [thread overview]
Message-ID: <20111205165021.GA24165@janus> (raw)
After upgrading 50+ NFSv3 (over UDP) client machines from 3.0.x to
3.1.4 I occasionally noticed a machine with lots of processes hanging
in __rpc_execute() for a specific mount point with no progress at all.
Stack:
[<c17fe7e0>] schedule+0x30/0x50
[<c177e259>] rpc_wait_bit_killable+0x19/0x30
[<c17feeb5>] __wait_on_bit+0x45/0x70
[<c177e240>] ? rpc_release_task+0x110/0x110
[<c17fef3d>] out_of_line_wait_on_bit+0x5d/0x70
[<c177e240>] ? rpc_release_task+0x110/0x110
[<c108aed0>] ? autoremove_wake_function+0x40/0x40
[<c177e89b>] __rpc_execute+0xdb/0x1a0
...
Every reference to the specific mount point on the client machine hangs
and the server does not receive any related network traffic. The server
works fine for other identical client machines with the same export mounted.
Other mounts on the (now) broken client still work. Killing the hanging
client processes repairs the situation.
This has happened a couple of times on client machines with heavy (NFS)
load. The mount-point has originally been mounted by the automounter.
--
Frank
next reply other threads:[~2011-12-05 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 16:50 Frank van Maarseveen [this message]
2011-12-05 23:39 ` 3.1.4: NFSv3 RPC scheduling issue? Trond Myklebust
2011-12-06 8:11 ` Frank van Maarseveen
2011-12-06 19:57 ` Trond Myklebust
2011-12-07 13:43 ` Frank van Maarseveen
2011-12-10 3:10 ` Trond Myklebust
2011-12-11 12:40 ` Frank van Maarseveen
2011-12-11 18:10 ` Frank van Maarseveen
2011-12-11 14:09 ` Frank van Maarseveen
2011-12-06 9:04 ` Frank van Maarseveen
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=20111205165021.GA24165@janus \
--to=frankvm@frankvm.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).