Home • Explore • Blog • CI
☰



man-pages
2nd chunk of `umount.man`
3f4a4f2c594d486b40c0164cf1487108f006e28cd18fc34f0000000100000d8a
           were unmounted earlier with the -n option.

       -f, --force
           Force an unmount (in case of an unreachable NFS system).

           Note that this option does not guarantee that umount command does
           not hang. It’s strongly recommended to use absolute paths without
           symlinks to avoid unwanted readlink(2) and stat(2) system calls on
           unreachable NFS in umount.

       -i, --internal-only
           Do not call the /sbin/umount.filesystem helper even if it exists. By
           default such a helper program is called if it exists.

       -l, --lazy
           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 umount -l 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.

       -N, --namespace ns
           Perform umount in the mount namespace specified by ns. ns is either
           PID of process running in that namespace or special file
           representing that namespace.

           umount switches to the namespace when it reads /etc/fstab, writes
           /etc/mtab (or writes to /run/mount) and calls umount(2) system call,
           otherwise it runs in the original namespace. It means that the
           target mount namespace does not have to contain any libraries or
           other requirements necessary to execute umount(2) command.

           See mount_namespaces(7) for more information.

       -n, --no-mtab
           Unmount without writing in /etc/mtab.

       -O, --test-opts option...
           Unmount only the filesystems that have the specified option set in
           /etc/fstab. More than one option may be specified in a
           comma-separated list. Each option can be prefixed with no to
           indicate that no action should be taken for this option.

       -q, --quiet
           Suppress "not mounted" error messages.

       -R, --recursive
           Recursively unmount each specified directory. Recursion for each
           directory will stop if any unmount operation in the chain fails for
           any reason. The relationship between mountpoints is determined by
           /proc/self/mountinfo entries. The filesystem must be specified by
           mountpoint path; a recursive unmount by device name (or UUID) is
           unsupported. Since version 2.37 it umounts also all over-mounted
           filesystems (more filesystems on the same mountpoint).

       -r, --read-only
           When an unmount fails, try to remount the filesystem read-only.

       -t, --types type...
           Indicate that the actions should only be taken on filesystems of the
           specified type. More than one type may be specified in a
           comma-separated list. The list of filesystem types can be prefixed
           with no to indicate that no action should be taken for all of the
           mentioned types. Note that umount reads information about mounted
           filesystems from kernel (/proc/mounts) and filesystem names
Title: umount Options (Continued)
Summary
Further options for `umount` include: `-f` (force unmount), `-i` (internal-only, skip helper calls), `-l` (lazy unmount for preventing hangs), `-N` (operate in a specific mount namespace), `-n` (no-mtab, don't write to /etc/mtab), `-O` (test-opts, unmount based on fstab options), `-q` (quiet, suppress errors), `-R` (recursive unmount), `-r` (read-only, remount read-only on failure), and `-t` (types, specify filesystem types to unmount). These options provide granular control over the unmounting process, allowing for handling various scenarios such as network shares, namespace operations, and specific filesystem types.