From: Peng Tao <bergwolf@gmail.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: client hang in lock_flocks()
Date: Mon, 4 Apr 2011 01:02:25 +0800 [thread overview]
Message-ID: <BANLkTimV2zSJ59b+JJLg2itTg5zzYhs30A@mail.gmail.com> (raw)
In-Reply-To: <20110403151229.GA13399@merit.edu>
Hi, Jim,
On Sun, Apr 3, 2011 at 11:12 PM, Jim Rees <rees@umich.edu> wrote:
> Peng Tao wrote:
>
> Would you please send the complete trace log, or maybe open a bugzilla
> entry and attach it there?
>
> Here is everything that was reported to me. I can ask for rpc info and a
> tcpdump if that would be useful.
Yes, rpc info is helpful. Please do
'echo 0 > /proc/sys/sunrpc/rpc_debug'
when the hang happens and upload /var/log/messages.
And corresponding nfs.ko and sunrpc.ko would help analysis too.
--
Thanks,
-Bergwolf
prev parent reply other threads:[~2011-04-03 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 16:52 client hang in lock_flocks() Jim Rees
[not found] ` <20110331165258.GA3048-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-04-03 1:37 ` Peng Tao
2011-04-03 15:12 ` Jim Rees
2011-04-03 17:02 ` Peng Tao [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=BANLkTimV2zSJ59b+JJLg2itTg5zzYhs30A@mail.gmail.com \
--to=bergwolf@gmail.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).