linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christopher Hawkins <chawkins@bplinux.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4 hang
Date: Fri, 21 May 2010 13:08:04 -0400	[thread overview]
Message-ID: <20100521170804.GA9639@fieldses.org> (raw)
In-Reply-To: <25273515.321274385268620.JavaMail.javamailuser@localhost>

On Thu, May 20, 2010 at 03:54:28PM -0400, Christopher Hawkins wrote:
> Hello, 
> 
> I have a bash script that sets up a root filesystem over NFS. The method works fine over NFS3 but hangs when using NFS4 as a transport. Hoping someone can help me figure out why?
> 
> In a nutshell:
> 
> 1. The node boots into a ramdisk that has a few thousand files in it already
> 2. connects to an NFS server exporting / and mounts that in a tmp dir
> 3. bash (on the booting node) loops through the local and remote filesystem and creates a local symlink to anything in the nfs root that it doesn't already have.

Wild.

> Export options are: / 192.168.1.0/24(rw,no_root_squash,no_subtree_check,fsid=0)
> Mount options are: rw,sync,noatime,rsize=1024,wsize=1024
> 
> rpcidmapd, portmap, statd are running on server and client, and rpc_pipefs is mounted on both as well. The script currently makes about 6200 links, total. Nfs4 hangs about 90% of the way through. I removed the directory it was hanging on (a simple, empty dir) and then it just hung on the next one.

Is it possible there's some idmap deadlock?  (If say an upcall to idmapd
is hanging because the mapping requires access to some file that isn't
there yet?)

A sysrq-T trace might help.

--b.

> Really appreciate any help or pointers on where to look for more info. Thanks!
> 
> Chris
> 
> 
>    
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-05-21 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3726796.301274385081605.JavaMail.javamailuser@localhost>
2010-05-20 19:54 ` nfs4 hang Christopher Hawkins
2010-05-21 17:08   ` J. Bruce Fields [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] <2212784.91274721147769.JavaMail.javamailuser@localhost>
2010-05-24 17:17 ` Christopher Hawkins
2010-05-27 17:08   ` J. Bruce Fields
2010-05-27 17:55     ` Trond Myklebust

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=20100521170804.GA9639@fieldses.org \
    --to=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).