From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: Christian Robottom Reis <kiko@canonical.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
NFS@lists.sourceforge.net,
Ronaldo Maia <romaia-Zkq4WM0RTTBfJ/NunPodnw@public.gmane.org>
Subject: Re: [NFS] Server-side locking issue
Date: Thu, 12 Jun 2008 18:42:49 -0400 [thread overview]
Message-ID: <4851A669.3020600@gmail.com> (raw)
In-Reply-To: <20080612214340.GA17293-Zkq4WM0RTTBfJ/NunPodnw@public.gmane.org>
Christian Robottom Reis wrote:
> On Fri, May 09, 2008 at 11:43:05AM -0400, J. Bruce Fields wrote:
>
>
>> Perhaps a sysrq-T dump of lockd would show where (and whether) it's
>> blocked? (So once lockd stops responding, log into the server, run
>> "echo t >/proc/sysrq-trigger", and collect the output from the logs,
>> especially the stacktrace for the lockd process).
>>
Sorry, I was debugging some other stuffs on my screen while mindlessly
reading the mailing list - somehow missed Bruce's original "sysrq-t"
paragraph. However, look like you've missed the "w" part. My guess is
that the lockd was spinning on the CPU when you hit the sysrq-t key or
your sysrq-t didn't run to its completion at all.
-- Wendy
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-06-12 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 22:18 [NFS] Server-side locking issue Christian Robottom Reis
[not found] ` <20080508221815.GB4583-Zkq4WM0RTTBfJ/NunPodnw@public.gmane.org>
2008-05-09 15:43 ` J. Bruce Fields
2008-06-12 21:43 ` Christian Robottom Reis
[not found] ` <20080612214340.GA17293-Zkq4WM0RTTBfJ/NunPodnw@public.gmane.org>
2008-06-12 22:17 ` Wendy Cheng
2008-06-12 22:42 ` Wendy Cheng [this message]
2008-06-12 23:50 ` Jeff Layton
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=4851A669.3020600@gmail.com \
--to=s.wendy.cheng@gmail.com \
--cc=NFS@lists.sourceforge.net \
--cc=bfields@fieldses.org \
--cc=kiko@canonical.com \
--cc=romaia-Zkq4WM0RTTBfJ/NunPodnw@public.gmane.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