mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: Neil Brown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.
Date: Mon, 20 Aug 2007 16:34:14 -0700	[thread overview]
Message-ID: <20070820233414.GM3956@digitalkingdom.org> (raw)
In-Reply-To: <18122.9034.504690.370294@notabene.brown>

On Tue, Aug 21, 2007 at 09:27:06AM +1000, Neil Brown wrote:
> On Monday August 20, rlpowell@digitalkingdom.org wrote:
> > (cc's to me appreciated)
> > 
> > It would be really, really nice if "umount -f" against a hung
> > NFS mount actually worked on Linux.  As much as I hate Solaris,
> > I consider it the gold standard in this case: If I say "umount
> > -f /mount/that/is/hung" it just goes away, immediately, and
> > anything still trying to use it dies (with EIO, I'm told).
> 
> Have you tried "umount -l"?   How far is that from your
> requirements?

I actually talked about that further down.  The short version: quite
far.

The long version:

It leaves a bunch of hung processes, with no real way for me to
determine which processes are hung on the now-non-existent mount,
and (at least with autofs) it leaves /etc/mtab in an inconsistent
state, so I had to edit it to restart autofs.  Only a mild
improvement on rebooting, says I.

Also, it took a really long time (minutes) to return.

> Alternately:
>    mount --move /problem/path /somewhere/else
>    umount -f /somewhere/else
>    umount -l /somewhere/else
> 
> might be a little closer to what you want.

I don't think that would solve the problem: the umount -f would
still hang and eventually return busy, fuser would still hang, and
umount -l would still leave inconsistent crap lying around.

> Though I agree that it would be nice if we could convince all
> subsequent requests to a server to fail EIO instead of just the
> currently active ones.  I'm not sure that just changing "umount
> -f" is the right interface though....  Maybe if all the server
> handles appeared in sysfs and have an attribute which you could
> set to cause all requests to fail...

I have no opinion on interface details, I simply know that on
Solaris, "umount -f" Just Works, and I would love to have similar
behaviour on Linux.

-Robin

-- 
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
Proud Supporter of the Singularity Institute - http://singinst.org/

  reply	other threads:[~2007-08-20 23:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 22:54 Robin Lee Powell
2007-08-20 23:27 ` Neil Brown
2007-08-20 23:34   ` Robin Lee Powell [this message]
2007-08-21  1:51     ` Salah Coronya
2007-08-21 16:43 ` John Stoffel
2007-08-21 16:55   ` J. Bruce Fields
2007-08-21 17:01   ` Peter Staubach
2007-08-21 17:14     ` Chakri n
2007-08-21 17:14     ` Robin Lee Powell
2007-08-21 17:18       ` Peter Staubach
2007-08-21 18:50     ` John Stoffel
2007-08-21 19:04       ` Peter Staubach
2007-08-21 19:25       ` J. Bruce Fields
2007-08-24 15:09         ` Ric Wheeler
2007-08-24 15:37           ` Peter Staubach
2007-08-24 15:53           ` J. Bruce Fields
2007-08-21 23:04       ` Valdis.Kletnieks
2007-08-22 10:03         ` Theodore Tso
2007-08-22 15:26         ` John Stoffel
2007-08-31  8:06       ` Ian Kent
2007-08-31 15:10         ` Valdis.Kletnieks
2007-08-31 15:30           ` 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=20070820233414.GM3956@digitalkingdom.org \
    --to=rlpowell@digitalkingdom.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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

all inboxes | Powered by JetHome®