From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christopher Hawkins <chawkins@bplinux.com>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: nfs4 hang
Date: Thu, 27 May 2010 13:55:01 -0400 [thread overview]
Message-ID: <1274982901.20557.1.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20100527170829.GA11559@fieldses.org>
On Thu, 2010-05-27 at 13:08 -0400, J. Bruce Fields wrote:
> On Mon, May 24, 2010 at 01:17:01PM -0400, Christopher Hawkins wrote:
> > Thanks Bruce, it does appear that idmapd is somehow related to this
> > issue. However, I'm stumped because it does exist on the client, along
> > with all the libraries it requires (according to ldd, anyway).
>
> And /etc/passwd, and whatever other files it might decide it needs to
> open to do its work?
>
> > Is
> > there an easy way to disable idmapd while still running nfs4 to
> > determine if it is causing the hang?
>
> Not that I know of.
Why would you need to? 'Magic sysrq-trigger t' will show you if the
idmapper is deadlocked inside the NFS filesystem (as will the equivalent
'echo t >/proc/sysrq-trigger').
Trond
next prev parent reply other threads:[~2010-05-27 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2212784.91274721147769.JavaMail.javamailuser@localhost>
2010-05-24 17:17 ` nfs4 hang Christopher Hawkins
2010-05-27 17:08 ` J. Bruce Fields
2010-05-27 17:55 ` Trond Myklebust [this message]
[not found] <23795442.851274476971674.JavaMail.javamailuser@localhost>
2010-05-21 21:24 ` Christopher Hawkins
2010-05-22 15:11 ` Christopher Hawkins
2010-05-24 17:14 ` J. Bruce Fields
[not found] <3726796.301274385081605.JavaMail.javamailuser@localhost>
2010-05-20 19:54 ` Christopher Hawkins
2010-05-21 17:08 ` J. Bruce Fields
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=1274982901.20557.1.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=chawkins@bplinux.com \
--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).