From: NeilBrown <neilb@suse.de>
To: Nathan Shearer <mail@nathanshearer.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: umount -f stalls forever
Date: Thu, 10 Jul 2014 15:11:12 +1000 [thread overview]
Message-ID: <20140710151112.7710bb7b@notabene.brown> (raw)
In-Reply-To: <53BDA2C7.4030007@nathanshearer.ca>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
On Wed, 09 Jul 2014 14:15:03 -0600 Nathan Shearer <mail@nathanshearer.ca>
wrote:
> When I have an nfs share that is mounted with the hard option (either
> explicitly or implicitly since hard is on by default), and the nfs
> server becomes unresponsive for any reason, it often causes the entire
> OS to hang on many operations. In some cases I cannot even reboot a
> server depending on what the nfs share was used for.
>
> I relaize that this was probably done intentionally to prevent data
> loss. However, when I am cleaning up a disaster and I actually do want
> to "umount -f" a stalled nfs share and data loss es acceptable, then I
> expect that command to return and the share to be unmounted. From a
> usability perspective, stalling forever when I am explicitly forcing an
> action is not right.
>
> There is a workaround: and that is to assign the IP of the nfs server to
> my system then issue umount -f, however that hardly the best way since I
> am changing my network topology to unmount an offline filesystem. In
> some situations adding an IP to an interface is not possilble, and if
> the system is a remote system it could lead to more problems since it is
> mostly unresponsive.
>
> It would be greatly appreciated if a patch could be introduced that
> allows "umount -f" to actually work without making any other changes to
> a running system. The man page for umount even states that the -f
> argument can be used to unmount an unreachable nfs share -- but it
> almost never works.
> --
> 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
Hi Nathan,
you don't say what kernel you are running....
A change was made in Linux 3.12 (8033426e6bdb2690d302872ac1e1fadaec1a5581)
which may address the problem you have.
So if you are using a kernel older than that, try a newer kernel.
This may not make "umount -f" work, but it should stop it from hanging.
To make it work you might need to kill all the processes using the mount
point first.
Also, "umount -l" might be a suitable answer to your problems.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-07-10 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 20:15 umount -f stalls forever Nathan Shearer
2014-07-10 5:11 ` NeilBrown [this message]
2014-07-14 17:29 ` Nathan Shearer
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=20140710151112.7710bb7b@notabene.brown \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=mail@nathanshearer.ca \
/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