Seth Woolley's Man Viewer

umount(8) - umount, umount - unmount file systems - man 8 umount

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

UMOUNT(8)                  Linux Programmer's Manual                 UMOUNT(8)

       umount - unmount file(1,n) systems

       umount [-hV]

       umount -a [-dflnrv] [-t vfstype] [-O options]
       umount [-dflnrv] dir | device [...]

       The  umount command detaches the file(1,n) system(s) mentioned from the file(1,n)
       hierarchy.  A file(1,n) system is specified by giving the directory where it
       has  been  mounted.  Giving the special device on which the file(1,n) system
       lives may also work, but is obsolete, mainly because it  will  fail  in(1,8)
       case this device was mounted on more than one directory.

       Note  that  a  file(1,n)  system cannot be unmounted when it is `busy' - for
       example, when there are open(2,3,n) files on it, or when some process has  its
       working  directory  there,  or  when  a swap file(1,n) on it is in(1,8) use.  The
       offending process could even be umount itself - it opens libc, and libc
       in(1,8)  its  turn may open(2,3,n) for example locale(3,5,7) files.  A lazy unmount avoids
       this problem.

       Options for the umount command:

       -V     Print version(1,3,5) and exit.

       -h     Print help message and exit.

       -v     Verbose mode.

       -n     Unmount without writing in(1,8) /etc/mtab.

       -r     In case unmounting fails, try to remount read-only.

       -d     In case the unmounted device was a loop device, also  free  this
              loop device.

       -i     Don't  call  the  /sbin/umount.<filesystem>  helper  even  if(3,n) it
              exists. By default /sbin/umount.<filesystem> helper is called if(3,n)
              one exists.

       -a     All  of  the  file(1,n) systems described in(1,8) /etc/mtab are unmounted.
              (With umount version(1,3,5) 2.7 and later: the proc(5,n) filesystem  is  not

       -t vfstype
              Indicate  that  the actions should only be taken on file(1,n) systems
              of the specified type.  More than one type may be specified in(1,8) a
              comma separated list.  The list of file(1,n) system types can be pre-
              fixed with no to specify the  file(1,n)  system  types  on  which  no
              action should be taken.

       -O options
              Indicate  that  the actions should only be taken on file(1,n) systems
              with the specified options in(1,8) /etc/fstab.  More than one  option
              type  may  be  specified in(1,8) a comma separated list.  Each option
              can be prefixed with no to specify options for which  no  action
              should be taken.

       -f     Force unmount (in(1,8) case of an unreachable NFS system).  (Requires
              kernel 2.1.116 or later.)

       -l     Lazy unmount. Detach the filesystem from the filesystem  hierar-
              chy now, and cleanup all references to the filesystem as soon as
              it is not busy anymore.  (Requires kernel 2.4.11 or later.)

       The umount command will free the loop device (if(3,n) any)  associated  with
       the mount(2,8), in(1,8) case it finds the option `loop=...' in(1,8) /etc/mtab, or when
       the -d option was given.  Any pending loop devices can be  freed  using
       `losetup -d', see losetup(8).

       /etc/mtab table of mounted file(1,n) systems

       umount(2), mount(2,8)(8), losetup(8).

       A umount command appeared in(1,8) Version 6 AT&T UNIX.

Linux 2.0                        26 July 1997                        UMOUNT(8)

References for this manual (incoming links)