From: Ben Greear <greearb@candelatech.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: 'umount -f /mnt/foo' fails if server IP is gone.
Date: Tue, 15 Oct 2013 11:29:51 -0700 [thread overview]
Message-ID: <525D899F.5010604@candelatech.com> (raw)
Is 'umount -f' supposed to always work, even if the file server
goes away?
I have a user's system that just hangs forever in this case.
Could be local changes we have made, but I'm curious about
the expected behaviour before I go digging too deep...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-10-15 18:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 18:29 Ben Greear [this message]
2013-10-17 17:35 ` 'umount -f /mnt/foo' fails if server IP is gone Ben Greear
2013-10-17 18:03 ` Chuck Lever
2013-10-17 18:08 ` Ben Greear
2013-10-17 18:16 ` Jeff Layton
2013-10-17 18:05 ` Myklebust, Trond
2013-10-17 18:11 ` Ben Greear
2013-10-17 18:23 ` Christopher T Vogan
2013-10-17 18:32 ` Myklebust, Trond
2013-10-17 18:35 ` Ben Greear
2013-10-17 18:42 ` Myklebust, Trond
2013-10-17 19:34 ` Ben Greear
2013-10-17 19:36 ` Ben Greear
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=525D899F.5010604@candelatech.com \
--to=greearb@candelatech.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).