UMOUNT(2) — HP-UX

NAME

umount − unmount a file system

SYNOPSIS

int umount (name)
char ∗name;

DESCRIPTION

Umount requests that a previously mounted file system contained on the block special device identified by name be unmounted. Name is a pointer to a path name. After unmounting the file system, the directory upon which the file system was mounted reverts to its ordinary interpretation.

Umount can also request that a file system mounted previously on the directory identified by name be unmounted. After unmounting the file system, name reverts to its ordinary interpretation.

Umount can be invoked only by the superuser.

NETWORKING FEATURES

NFS

Path must indicate a directory name when unmounting an NFS file system.

RETURN VALUE

If successful, umount returns a value of 0. Otherwise, it returns a value of −1 and sets errno to indicate the error.

ERRORS

Umount fails if one or more of the following are true:

[EPERM] The effective user ID of the process is not that of the superuser.

[ENOENT] Name does not exist.

[ENOTBLK] Name is not a block special device.

[EINVAL] Name is not mounted.

[EBUSY] A file on name is busy.

[EFAULT] Name points outside the allocated address space of the process. Reliable detection of this error is implementation dependent.

[ENXIO] The device associated with name does not exist.

[ENOTDIR] A component of name is not a directory.

[ENOENT] Name is null.

[ENAMETOOLONG]
Name exceeds MAXPATHLEN characters.

[EACCESS] A component of the path prefix of name denies search permission.

[ELOOP] Too many symbolic links were encountered in translating the path name.

WARNINGS

If umount is called from the program level (that is, not from the mount(1M) level), the table of mounted devices contained in /etc/mnttab is not updated automatically.

DEPENDENCIES

Series 300 Diskless
When umount is called from a diskless node and path refers to a block-special file, path is interpreted from the root server. This behavior is subject to change in future releases, and its use in applications is not recommended.

When umount is called from a diskless node and path refers to a directory on which is mounted a UFS file system (as opposed to an NFS file system; see vfsmount(2)), an EINVAL error is returned. This behavior is subject to change in future releases, and its use in applications is not recommended.

Series 500
Path must specify a block special file, not a directory.

Museum

Related Articles