umount_vxfs - unmount a VxFS file system

umount [ -F vxfs] [ generic_options ] [ -o [ force ]]

{ special | mount_point }

VRTSvxfs

umount notifies the system that special, a VxFS block special device, is no longer available to users from mount_point.

If a file system has mounted Storage Checkpoints, all Storage Checkpoints must be unmounted before unmounting the file system.

The umount command operates in the same way on cluster file systems. However, when a primary file system is unmounted and all other nodes have mounted the file ssytem with the seconly option, all seconly mounts are disabled.

generic_options
	Supported by the generic umount command. See the mount(1M) manual page.
-F vxfs	Specifies the VxFS file system type.
-o	Specifies the VxFS-specific options in a comma-separated list. The available options are: force Unmounts a VxFS file system even if it contains busy files. Caution: Using the force option can corrupt data in open files. If force is not specified, umount does not unmount the file system if it contains any busy files. Programs that try to access files after a file system is forcibly unmounted receive an EIO error. If a file system has mounted Storage Checkpoints, that file system can be unmounted only after all of its Storage Checkpoints are unmounted, even if the force option is specified. mntunlock=ID   Unmounts a file system that was mounted with the mntlock=ID option. The /etc/mnttab entry for the file system shows whether the file system was mounted with the mntlock option. The specified identifier, ID, must match the identifier specified with the mntlock option that was used to lock the mount point.

Only a privileged user can unmount file systems.

/etc/mnttab	Table of mounted file systems.

fsadm_vxfs(1M), mkfs_vxfs(1M), mount(1M), mount_vxfs(1M), qiomkfile(1M), setmnt(1M), fsync(2), setuid(2), fs_vxfs(4), mnttab(4), vxfsio(7)