5113bc
From 0ae2aa6a43a852cb0326faade1532c02aa7617a4 Mon Sep 17 00:00:00 2001
5113bc
From: Karel Zak <kzak@redhat.com>
5113bc
Date: Fri, 20 Apr 2018 09:50:04 +0200
5113bc
Subject: [PATCH 156/173] umount: add note about --lazy
5113bc
5113bc
Unfortunately, it's pretty common that users on production systems use
5113bc
lazy umount to fix some FS issues. The usual result is unwanted system
5113bc
reboot, because -l is not the right way how to fix unreachable NFS or
5113bc
mess with local FS with submounts.
5113bc
5113bc
Note that after lazy umount /proc/self/mountinfo does not contain the
5113bc
FS entry, but kernel still references the FS. It makes it very
5113bc
difficult to debug.
5113bc
5113bc
Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1566674
5113bc
Suggested-by:  Steve Dickson <steved@redhat.com>
5113bc
Signed-off-by: Karel Zak <kzak@redhat.com>
5113bc
Upstream: http://github.com/karelzak/util-linux/commit/031800ff6c66b4d62229cfd116195950a718a21c
5113bc
---
5113bc
 sys-utils/umount.8 | 10 +++++++++-
5113bc
 1 file changed, 9 insertions(+), 1 deletion(-)
5113bc
5113bc
diff --git a/sys-utils/umount.8 b/sys-utils/umount.8
5113bc
index f0a712b06..71c2155b4 100644
5113bc
--- a/sys-utils/umount.8
5113bc
+++ b/sys-utils/umount.8
5113bc
@@ -54,7 +54,8 @@ working directory there, or when a swap file on it is in use.  The
5113bc
 offending process could even be
5113bc
 .B umount
5113bc
 itself - it opens libc, and libc in its turn may open for example locale
5113bc
-files.  A lazy unmount avoids this problem.
5113bc
+files.  A lazy unmount avoids this problem, but it may introduce another
5113bc
+issues. See \fB\-\-lazy\fR description bellow.
5113bc
 .SH OPTIONS
5113bc
 .TP
5113bc
 \fB\-a\fR, \fB\-\-all\fR
5113bc
@@ -107,6 +108,13 @@ Unmount without writing in
5113bc
 Lazy unmount.  Detach the filesystem from the filesystem hierarchy now,
5113bc
 and cleanup all references to the filesystem as soon as it is not busy
5113bc
 anymore.  (Requires kernel 2.4.11 or later.)
5113bc
+
5113bc
+A system reboot would be expected in near future if you're going to use this
5113bc
+option for network filesystem or local filesystem with submounts.  The
5113bc
+recommended use-case for \fBumount -l\fR is to prevent hangs on shutdown due to
5113bc
+an unreachable network share where a normal umount will hang due to a downed
5113bc
+server or a network partition. Remounts of the share will not be possible.
5113bc
+
5113bc
 .TP
5113bc
 \fB\-O\fR, \fB\-\-test\-opts\fR \fIoptions,list\fR
5113bc
 Indicate that the actions should only be taken on file systems with the
5113bc
-- 
5113bc
2.14.4
5113bc