From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: tim.gardner@canonical.com
Cc: linux-nfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
neilb@suse.de, bfields@fieldses.org, Trond.Myklebust@netapp.com
Subject: Re: nfsd deadlock, 2.6.36-rc3
Date: Fri, 3 Sep 2010 21:12:43 +0200 [thread overview]
Message-ID: <201009032112.43524.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4C7E73CB.7030603@canonical.com>
On środa, 1 września 2010 o 17:39:55 Tim Gardner wrote:
> I've been pursuing a simple reproducer for an NFS lockup that shows up
> under stress. There is a bunch of info (some of it extraneous) in
> http://bugs.launchpad.net/bugs/561210. I can reproduce it by writing
> loop mounted NFS exports:
>
> /etc/fstab: 127.0.0.1:/srv /mnt/srv nfs rw 0 2
> /etc/exports: /srv 127.0.0.1(rw,insecure,no_subtree_check)
>
> See the attached scripts test_master.sh and test_client.sh. I simply
> repeat './test_master.sh wait' until nfsd locks up, typically within 1-3
> cycles, e.g.,
>
> cd /mnt/srv
> while true; do ./test_master.sh wait; done
>
> Note that this test will run indefinitely if invoked from /srv, e.g.,
>
> cd /srv
> while true; do ./test_master.sh wait; done
>
> This issue, or something like it, appears to exist as far back as I've
> tested (Ubuntu Lucid 2.6.32.21). For now I'm assuming that, since the
> symptoms are similar, any lockup bug found in -rc3 is the likely culprit.
>
> See attached dmesg and config. Debug options of interest that I've
> enabled are CONFIG_DEBUG_SLAB, CONFIG_DEBUG_SLAB_LEAK,
> CONFIG_DEBUG_SPINLOCK, CONFIG_DEBUG_MUTEXES.
>
> dmesg.txt contains the initial 'INFO: task nfsd:1263 blocked for more
> than 120 seconds.' complaints as well as information dumped from
>
> echo d | sudo tee /proc/sysrq-trigger
> echo w | sudo tee /proc/sysrq-trigger
>
> Anything else I can provide?
>
> rtg
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=17762
for your bug report, please add your address to the CC list in there, thanks!
--
Maciej Rutecki
http://www.maciek.unixy.pl
prev parent reply other threads:[~2010-09-03 19:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 15:39 nfsd deadlock, 2.6.36-rc3 Tim Gardner
2010-09-01 16:54 ` J. Bruce Fields
2010-09-01 20:55 ` Neil Brown
2010-09-01 21:05 ` J. Bruce Fields
2010-09-01 21:11 ` Tim Gardner
2010-09-01 21:13 ` J. Bruce Fields
2010-09-02 15:13 ` Tim Gardner
2010-09-08 16:52 ` Tim Gardner
2010-09-08 17:50 ` J. Bruce Fields
2010-09-03 19:12 ` Maciej Rutecki [this message]
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=201009032112.43524.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tim.gardner@canonical.com \
/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.