All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Marion <mmarion@qualcomm.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Umount call getting stuck, hanging nfs?
Date: Mon, 8 May 2006 16:34:38 -0700	[thread overview]
Message-ID: <20060508233437.GG9873@cornholio.qualcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605050955571.2898@raven.themaw.net>

On Fri, May 05, 2006 at 09:59:14AM +0800, Ian Kent wrote:

> I think that might be the other way around.

You mean rpciod is already hung before the umount, and the umount is
then hung due to the rpciod?

> > /bin/umount //usr/local/projects/dsp/qdsp6
> > 
> > root      6270  0.0  0.0     0    0 ?        D    Apr28   3:17 [rpciod]
> > 
> > unfortunately, once this happens, any new mounts will fail.  Can't even
> > stat the path above via df.  Basically the whole NFS layer is stuck.
> 
> Tell us what the maps look like.

The noted path is like this:
/prj/dsp/qdsp6 -rw,acdirmin=1,acdirmax=5,acregmin=1,acregmax=5,rsize=32768,wsize=32768,noquota
western:/vol/eng_aus_0004/qdsp6

And the rest of the file is very similar.  The huge amount of options
came from trial and error with performance problems we were having, and
they're defaulting to tcp mounts.  The odd thing is that we basically
never have mounts hanging off this /prj tree in San Diego, or any other
office except for one.  And it's only hanging when talking to their 2
local NetApp filers.

-- 
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
A nerd is someone whose life revolves around computers and technology.
A geek is someone whose life revolves around computers and technology... 
and likes it!  - Stolen from a /. post.

  reply	other threads:[~2006-05-08 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 20:41 Umount call getting stuck, hanging nfs? Mike Marion
2006-05-04 21:20 ` Jeff Moyer
2006-05-04 22:07   ` Mike Marion
2006-05-05  1:59 ` Ian Kent
2006-05-08 23:34   ` Mike Marion [this message]
2006-05-09  1:31     ` Mike Marion
2006-05-09 11:21     ` Ian Kent

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=20060508233437.GG9873@cornholio.qualcomm.com \
    --to=mmarion@qualcomm.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.