*** UNIX MANUAL PAGE BROWSER ***

vold(8) System Manager's Manual vold(8) NAME vold - Logical Storage Manager configuration daemon SYNOPSIS /sbin/vold [ -kfd ] [ -r reset ] [ -m mode ] [ -x debug ] [ -D diag_portal ] [ -R request_portal ] DESCRIPTION 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 configu- ration changes, and communicates those changes to the kernel and modi- fies configuration information stored on disk. vold is also responsi- ble for initializing the Logical Storage Manager when the system is booted. The vold utility has the following options: If a vold process is run- ning 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 com- pletes. This is equivalent to -m disable, which starts vold in dis- abled mode. Reset all Logical Storage Manager configuration informa- tion 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 operat- ing 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 op- tion as part of a command sequence to completely reinitialize the Logi- cal 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 demon- stration 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. Other Logical Storage Manager utilities can detect when they are connected to a vold that is running in stubbed mode. When a utility detects a stubbed-mode vold, it will normally stub out any direct use of volume or plex devices, itself. This allows regular utilities to be used for making configuration changes in a testing environment that runs without any communication with the kernel or creation of real volume or plex devices. Specify the pathname to use for the volboot file. The default path is /etc/vol/volboot. This is primarily of use with the stub debug option. The volboot file contains an initial list of disks that are used to locate the root disk group. It also contains a host ID that is stored on disks in imported disk groups to define ownership of disks as a sanity check for disks that might be ac- cessible from more than one host. Specify a directory pathname to prefix for any disk device accessed by vold. For example, with devprefix=/tmp, any access to a raw disk device named rz3c would actually be directed to the file /tmp/dev/rrzc3. In stubbed-mode, vold can operate with such files being regular files. vold only requires entries in the prefixdir/dev direc- tory in stubbed mode. Log all possible tracing information in the given file. Flush tracefile data to disk, with fsync(2), to ensure that the last entry will be included in the file, even if the system crashes. Specify a rendezvous file pathname for di- agnostic operation connections to vold. By default, /etc/vol/vold_diag is used. The diagnostic portal exists in both the enabled and disabled operating modes. Specify a ren- dezvous file pathname for regular configuration and query re- quests. By default, this is /etc/vol/vold_request. The regular request portal exists only when vold is operating in enabled mode. ERRORS If errors are encountered, vold writes diagnostic messages to the stan- dard error output. Some serious errors will cause vold to exit. If an error is encountered when importing the rootdg disk group during a nor- mal 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 vold are as follows: (0) The requested startup mode completed successfully. This is re- turned if -f is not used to startup vold as a foreground process. If vold is started as a foreground process, then it will exit with a zero status if voldctl stop is used to cause vold to exit. (1) The command line usage is incorrect. (2) Enabled-mode operation was requested, but an error caused vold to enter disabled mode instead. This is also returned for boot- mode operation if startup failed. However, with boot-mode oper- ation, the background vold process exits as well. (3) The -k option was specified, but the existing vold could not be killed. (4) A system error was encountered that vold cannot recover from. The specific operation that failed is printed on the standard error output. (5) The background vold process was killed by a signal before startup completed. The specific signal is printed on the stan- dard error output. (6) A serious inconsistency was found in the kernel, preventing sane operation. This can also happen because of version mismatch be- tween the kernel and vold. (7) Logical Storage Manager configuration information could not be reset, because a volume or plex is in use. (8) Interprocess communication failure. (9) The rootdg disk group could not be modified during system re- boot. The system is brought to single-user mode. RELATED INFORMATION volintro(8), voldctl(8). delim off vold(8)