vold - Logical Storage Manager configuration daemon
/sbin/vold [-kfd] [-r reset] [-m mode] [-x debug] [-D diag_portal] [-R request_portal]
The Logical Storage Manager configuration daemon, vold, is responsible for maintaining configurations of disks and disk groups in the Logical Storage Manager. vold takes requests from other utilities for configuration changes, and communicates those changes to the kernel and modifies configuration information stored on disk. vold is also responsible for initializing the Logical Storage Manager when the system is booted.
The vold utility has the following options: If a vold process is running already, then kill it before any other startup processing. This is useful for recovering from a hung vold process. Killing the old vold and starting a new one should not cause any problems for volume or plex devices that are being used by applications or that contain mounted file systems. Start vold in the foreground. This is often useful when debugging vold, or when tracing configuration changes. If this flag is not used, vold will fork a background daemon process. The foreground process will exit as soon as vold startup processing completes. This is equivalent to -m disable, which starts vold in disabled mode. Reset all Logical Storage Manager configuration information stored in the kernel as part of startup processing. This will fail if any volume or plex devices are currently in use. This option is primarily useful for testing or debugging. Set the initial operating mode for vold. Possible values for mode are: Start fully enabled (default). This will use the volboot file to bootstrap and load in the rootdg disk group. It will then scan all known disks looking for disk groups to import, and will import those disk groups. This will also set up the /dev/vol, /dev/rvol, and /dev/plex directories to define all of the accessible volume and plex devices. If the /etc/vol/volboot file cannot be read or if the rootdg disk group cannot be imported, vold will be started in disabled mode. Start in disabled mode. This creates a rendezvous file for utilities that perform various diagnostic or initialization operations. This can be used with the -r reset option as part of a command sequence to completely reinitialize the Logical Storage Manager configuration. Use the voldctl enable operation to enable vold. Turn on various parameters used for debugging. The debug option argument is a number, which will set a tracing output level, or one of the following strings: This vold invocation will not communicate configuration changes to the kernel. It is typically used as a demonstration mode of operation for vold. In most aspects, a stubbed vold will act like a regular vold, except that disk devices can be regular files and volume and plex device nodes are not created. A stubbed vold can run concurrently with a regular vold, or concurrently with any other stubbed vold processes, as long as different rendezvous, volboot, and disk files are used for each concurrent process.
If errors are encountered, vold writes diagnostic messages to the standard error output. Some serious errors will cause vold to exit. If an error is encountered when importing the rootdg disk group during a normal startup, vold will enter disabled mode. Consult the error messages section of the manual Logical Storage Manager for a description of the diagnostics and the suggested course of action.
Defined exit codes for
are as follows:
The requested startup mode completed successfully. This is
is not used to startup
as a foreground process. If
is started as a foreground
process, then it will exit with a zero status if
is used to cause
The command line usage is incorrect.
Enabled-mode operation was requested,
but an error caused
mode instead. This is also returned for
boot-mode operation if startup failed. However, with
boot-mode operation, the background
process exits as well.
option was specified, but the existing
could not be killed.
A system error was encountered that
cannot recover from. The specific operation that failed is printed on the
standard error output.
process was killed
by a signal before startup completed. The specific signal is printed on the
standard error output.
A serious inconsistency was found in the kernel, preventing
sane operation. This can also happen because of version mismatch between
the kernel and
Logical Storage Manager configuration information
could not be reset, because a volume or plex is in use.
Interprocess communication failure.
disk group could not be modified
during system reboot. The system is brought to single-user mode.