From: David Jeffery <david_jeffery@adaptec.com>
To: nfs@lists.sourceforge.net
Subject: nfs client process/rpciod deadlock
Date: 24 Sep 2003 07:40:11 -0400 [thread overview]
Message-ID: <1064403611.620.168.camel@blackmagic> (raw)
Please CC: me as I am not subscribed to this list.
I have a problem with processes hanging in D state on a linux nfs
client. Both linux client and server are stock kernel.org 2.4.22
kernels with no extra drivers or patches. This problem is not new and
exists on older kernel.org and red hat kernels I have used.
The full setup is a smp linux nfs server, linux nfs client, and a few
other unix clients. Both linux systems have kernels without highmem.
The problem occurs with both SMP and UP kernels on the client. When
placed under load, the linux client will periodically get processes
stuck in D state. The processes stuck in D state will be one or more
work processes and rpciod.
Using sysrq-T to show state shows the deadlocked processes to be waiting
on a locked page in ___wait_on_page. (I have the full show state if
someone wants to see it.)
rpciod D F7FBF0A0 4468 749 1 777 750 (L-TLB)
Call Trace:
[___wait_on_page+158/192]
[truncate_list_pages+387/464]
[e100:e100_manage_adaptive_ifs+753/816]
[truncate_inode_pages+94/112]
[iput+201/544]
[nfs3_xdr_commitres+173/224]
[nfs_commit_done+550/1072]
[nfs3_xdr_commitres+0/224]
[__rpc_execute+554/688]
[schedule+756/800]
[__rpc_schedule+179/288]
[rpciod+184/496]
[arch_kernel_thread+38/64]
[rpciod+0/496]
javac D F33D5D40 0 3830 3829 3833 (NOTLB)
Call Trace:
[___wait_on_page+158/192]
[do_generic_file_read+756/1088]
[generic_file_read+137/352]
[file_read_actor+0/176]
[nfs_file_read+146/160]
[sys_read+152/240]
[system_call+51/64]
cp D F33D5DC0 0 3915 3525 (NOTLB)
Call Trace:
[___wait_on_page+158/192]
[do_generic_file_read+756/1088]
[generic_file_read+137/352]
[file_read_actor+0/176]
[nfs_file_read+146/160]
[sys_read+152/240]
[system_call+51/64]
Is this related to the comment in fs/nfs/write.c or is this a different
race condition?
/*
* Update attributes as result of writeback.
* FIXME: There is an inherent race with invalidate_inode_pages and
* writebacks since the page->count is kept > 1 for as long
* as the page has a write request pending.
*/
I'd be happy to test patches. It can take up to a week for the problem
to occur but it has become more frequent with the loads we're putting on
the machine.
David Jeffery
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-09-24 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 11:40 David Jeffery [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-25 16:24 nfs client process/rpciod deadlock Lever, Charles
2003-09-26 17:02 ` David Jeffery
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=1064403611.620.168.camel@blackmagic \
--to=david_jeffery@adaptec.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 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.