From: Nikolaus Rath <Nikolaus@rath.org>
To: linux-nfs@vger.kernel.org
Subject: Client hangs in __mutex_lock_slowpath, network connection maxed out
Date: Thu, 03 Feb 2011 13:04:55 -0500 [thread overview]
Message-ID: <4D4AEE47.8080504@rath.org> (raw)
Hello,
I'm mounting an NFS4 volume from a kernel 2.6.32-27 server in a
2.6.37-020637rc2 client.
Very often, when there is significant IO on the mounted volume, the
client hangs. The process accessing the mountpoint is stuck in D
state. Any more attempts to access the mountpoint get stuck in D state
as well. Shortly after, the kernel reports the task as hanging:
[ 3120.620125] Call Trace:
[ 3120.620138] [<c05ec44d>] ? _raw_spin_lock+0xd/0x10
[ 3120.620146] [<c05eb4b6>] __mutex_lock_slowpath+0xc6/0x120
[ 3120.620152] [<c05eb1c5>] mutex_lock+0x25/0x40
[ 3120.620158] [<c022e3b3>] do_lookup+0xc3/0x120
[ 3120.620164] [<c022fbb2>] link_path_walk+0x402/0x9b0
[ 3120.620171] [<c0167b5a>] ? queue_work+0x1a/0x20
Additional tasks hang at a slightly different point:
[ 3120.620304] [<f90b863d>] ? nfs_access_add_cache+0xcd/0x120 [nfs]
[ 3120.620326] [<f90b8709>] ? nfs_do_access+0x79/0xc0 [nfs]
[ 3120.620333] [<c05eb4b6>] __mutex_lock_slowpath+0xc6/0x120
[ 3120.620339] [<c05eb1c5>] mutex_lock+0x25/0x40
[ 3120.620344] [<c022e3b3>] do_lookup+0xc3/0x120
[ 3120.620350] [<c022fbb2>] link_path_walk+0x402/0x9b0
[ 3120.620356] [<c0230697>] path_walk+0x47/0xa0
[ 3120.620361] [<c0230819>] do_path_lookup+0x59/0xb0
[ 3120.620367] [<c02311ff>] user_path_at+0x3f/0x70
[ 3120.620374] [<c02005b8>] ? do_linear_fault+0x58/0x70
[ 3120.620380] [<c020133a>] ? handle_mm_fault+0xda/0x230
[ 3120.620387] [<c0228899>] vfs_fstatat+0x49/0x70
Finally, the client saturates the 100 MBit connection with sending and
receiving from the NFS server. I'm pretty sure this is garbage data,
even if the client would copy the entire mountpoint there wouldn't be
that much data to copy.
There are no visible symptoms on the server.
Anyone able to help?
Thanks,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
next reply other threads:[~2011-02-03 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 18:04 Nikolaus Rath [this message]
2011-02-03 18:14 ` Client hangs in __mutex_lock_slowpath, network connection maxed out J. Bruce Fields
2011-02-03 20:17 ` Trond Myklebust
2011-02-03 20:10 ` 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=4D4AEE47.8080504@rath.org \
--to=nikolaus@rath.org \
--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).