mountall(1M) — ADMINISTRATOR COMMANDS
NAME
mountall, umountall − mount, unmount multiple file systems
SYNOPSIS
mountall [−F FSType] [−l | −r] [−s strategy] [−n number] [file-system-table]
umountall [−F FSType] [−k] [−l | −r]
DESCRIPTION
These commands may be executed only by a privileged user.
mountall is used to mount file systems according to a file-system-table. (/etc/vfstab is the default file system table.) The special file name "−" reads from the standard input. If the dash is specified, then the standard input must be in the same format as /etc/vfstab.
Before each file system is mounted, a sanity check is done using fsck [see fsck(1M)] to see if it appears mountable. If the file system does not appear mountable, it is fixed, using fsck, before the mount is attempted.
umountall causes all mounted file systems except root, /proc, /var, and /usr to be unmounted. If the FSType is specified mountall and umountall limit their actions to the FSType specified.
The options are:
−F Specify the File System type to be mounted or unmounted. If FSType is specified the action is limited to file systems of this FSType.
−k Send a SIGTERM, followed by a SIGKILL signal to processes that are using the filesystem. There is no guarantee that this will terminate every process that might cause a filesystem to be busy.
−l Limit the action to local file systems.
−n Specify a numeric argument. This may only be used with the disk-busy strategy: it specifies the maximum number of disks that may be checked in parallel. If it is not specified, all disks with file systems requiring checking will be checked in parallel.
−r Limit the action to remote file system types.
−s Specifies the strategy to be used when checking file systems. More information on the mountall strategies can be found in the mountall section below.
MOUNTALL
The mountall program is capable of checking and repairing file systems using several different strategies.
The basic strategy is sequential: file systems are checked one at a time in the order they are found in the file-system-table.
The next strategy is fsck-pass; the fsck-pass strategy checks the file systems with their file-system-table fsck pass numbers of two or greater in parallel, grouped by the fsck pass numbers. Only local file systems may be checked in parallel; the fsck pass number information will be ignored for remote file systems.
File systems with fsck pass numbers of 0 and 1 will be checked in sequential order in the fashion of the sequential strategy; those with fsck pass numbers of two or greater will be checked in parallel.
All file systems assigned to the same fsck pass number will have their fsck(1M) operations started simultainiously. mountall will then wait for all of the fsck(1M) operations started at the beginning of a pass to be completed before it starts the next pass.
To obtain the best performance, only one fsck(1M) operation should be performed on a disk at one time. The file systems being checked in parallel should be grouped by size as closely as possible. Checking too many file systems in parallel may actually slow down the overall process; start with 2 or 3 at a time.
The final strategy is disk-busy. The disk-busy strategy ignores the fsck pass number information and attempts to determine if all of the local file systems are located on properly named, real disk devices. If all of the local file systems aren’t located on properly named, real disk devices, mountall will switch to the fsck-pass strategy. If all of the local file systems are acceptable, the disk-busy strategy will attempt to keep one fsck operation running on each disk device as long as there is a file system that needs to be checked.
If all of the file systems on a system are located on real disk drives, this strategy should perform the required fsck operations in the minimum amount of time.
To change the strategy used when the system checks its file systems on reboot, edit the file /etc/rc2.d/S01MOUNTFSYS and add the −s option with the desired strategy argument to the line that starts with /sbin/mountall.
DEFAULT STRATEGY
The /sbin/mountall program will default to using the disk-busy strategy if the VERITAS Volume Manager (VxVM) package is in the kernel and the fsck-pass strategy otherwise.
DIAGNOSTICS
No messages are printed if the file systems are mountable and clean.
Error and warning messages come from fsck(1M) and mount(1M).