offending process could even be
.B umount
itself - it opens libc, and libc in its turn may open for example locale
-files. A lazy unmount avoids this problem.
+files. A lazy unmount avoids this problem, but it may introduce another
+issues. See \fB\-\-lazy\fR description bellow.
.SH OPTIONS
.TP
.BR \-a , " \-\-all"
Lazy unmount. Detach the filesystem from the file hierarchy now,
and clean up all references to this filesystem as soon as it is not busy
anymore.
+
+A system reboot would be expected in near future if you're going to use this
+option for network filesystem or local filesystem with submounts. The
+recommended use-case for \fBumount -l\fR is to prevent hangs on shutdown due to
+an unreachable network share where a normal umount will hang due to a downed
+server or a network partition. Remounts of the share will not be possible.
+
.TP
.BR \-n , " \-\-no\-mtab"
Unmount without writing in