From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: NeilBrown <neilb@suse.com>
Cc: mtk.manpages@gmail.com, systemd-devel@freedesktop.org,
linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH manpages] umount.2: revise MNT_FORCE description.
Date: Tue, 8 Aug 2017 21:26:54 +0200 [thread overview]
Message-ID: <508034ae-e254-d0bd-5ca9-c3f1959f8fe5@gmail.com> (raw)
In-Reply-To: <87mv7asj5l.fsf@notabene.neil.brown.name>
On 08/08/2017 07:49 AM, NeilBrown wrote:
>
> MNT_FORCE does not allow a busy filesystem to be unmounted. Only
> MNT_DETACH allows that.
> MNT_FORCE only tries to abort pending transactions, in the hope that
> might help umount not to block,
>
> Also, other filesystems than NFS support MNT_FORCE.
>
> Signed-off-by: NeilBrown <neilb@suse.com>
Thanks, Neil. Applied.
Cheers,
Michael
> ---
>
> Explanation derived from examination of source code.
> Cc to systemd devel in relation to comment I just posted:
>
> https://github.com/systemd/systemd/commit/0c08f5cde749bd2818475e487109cd0d413452df
>
> You may want to move the "linux version when support was added" to a
> comment, or discard it.
>
> man2/umount.2 | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/man2/umount.2 b/man2/umount.2
> index 68f76b7c6352..ccd1d07afe88 100644
> --- a/man2/umount.2
> +++ b/man2/umount.2
> @@ -61,9 +61,17 @@ unmounts a target, but allows additional
> controlling the behavior of the operation:
> .TP
> .BR MNT_FORCE " (since Linux 2.1.116)"
> -Force unmount even if busy.
> -This can cause data loss.
> -(Only for NFS mounts.)
> +Ask the filesystem to abort pending requests before attempting the
> +unmount. This may allow the unmount to complete without waiting
> +for an inaccessible server. If, after aborting requests, some
> +processes still have active references to the filesystem, the
> +unmount will still fail. In Linux 4.12, only the filesystems
> +9p (2.6.16),
> +ceph (2.6.34),
> +cifs (2.6.12),
> +fuse (2.6.16),
> +lustre (3.11),
> +and NFS (2.1.116) respond to MNT_FORCE.
> .TP
> .BR MNT_DETACH " (since Linux 2.4.11)"
> Perform a lazy unmount: make the mount point unavailable for new
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2017-08-08 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 5:49 [PATCH manpages] umount.2: revise MNT_FORCE description NeilBrown
2017-08-08 19:26 ` Michael Kerrisk (man-pages) [this message]
2017-08-10 3:23 ` [PATCH manpages] umount.2: restore mention of data loss with MNT_FORCE NeilBrown
2017-08-12 20:07 ` Michael Kerrisk (man-pages)
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=508034ae-e254-d0bd-5ca9-c3f1959f8fe5@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=neilb@suse.com \
--cc=systemd-devel@freedesktop.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).