voldctl(8)voldctl(8)NAMEvoldctl - Controls the Logical Storage Manager volume configuration
daemon
SYNOPSIS
/sbin/voldctl init [hostid]
/sbin/voldctl hostid hostid
/sbin/voldctl add disk accessname [attr[=value]]...
/sbin/voldctl rm disk accessname...
/sbin/voldctl list
/sbin/voldctl enable
/sbin/voldctl disable
/sbin/voldctl [-k] stop
/sbin/voldctl mode
/sbin/voldctl license [init]
DESCRIPTION
The voldctl utility manages some aspects of the state of the Logical
Storage Manager volume configuration daemon, vold, and manages configu‐
ration aspects related to bootstrapping the rootdg disk group configu‐
ration.
A key part of the state of vold and of bootstrapping the rootdg disk
group is the /etc/vol/volboot file. This file contains a host ID, which
is usually the host name, which LSM uses to establish ownership of
physical disks. This host ID is used to ensure that two or more hosts
that can access disks on a shared SCSI bus will not interfere with each
other in their use of those disks. This host ID is also important in
the generation of some unique ID strings that are used internally by
the Logical Storage Manager for stamping disks and disk groups.
The /etc/vol/volboot file might also contain a list of disks to scan in
search of the rootdg disk group. This list is needed only if the auto‐
configuration functionality of LSM is disabled (see vold(8) for
details). At least one disk in the list must be both readable and a
part of the rootdg disk group, or the Logical Storage Manager will not
be able to start up correctly.
The vold daemon operates in one of three modes: enabled, disabled, or
booted. The enabled state is the normal operating state. Most configu‐
ration operations are allowed in the enabled state. Entering the
enabled state imports all disk groups that were previously imported on
this host, and begins the management of device nodes stored in the
/dev/vol and /dev/rvol directories.
In the disabled state, vold does not retain configuration information
for the imported disk groups, and does not maintain the volume device
directories. Most operations are disallowed in the disabled state. Cer‐
tain failures, most commonly the loss of all disks or configuration
copies in the rootdg disk group, will cause vold to enter the disabled
state automatically.
The booted state is entered as part of normal system startup, prior to
checking the root file system (see fsck(8)). Entering the booted mode
imports the rootdg disk group, and then waits for a request to enter
the enabled mode. The volume device node directories are not maintained
in booted mode, because it might not be possible to write to the root
file system.
KEYWORDS
The action performed by voldctl depends upon the keyword specified as
the first operand. Supported keywords are: Reinitializes the
/etc/vol/volboot file with a new host ID (which is usually the host
name), and an empty list of disks. If a hostid operand is specified,
this string is used; otherwise, a default host ID is used. On systems
with a hardware-defined system ID, the default host ID might be derived
from this hardware ID. Changes the host ID, which is usually the host
name, in the /etc/vol/volboot file and on all disks in disk groups cur‐
rently imported on this machine. You might want to change the Logical
Storage Manager host ID for your machine if you are also changing the
network node name of your machine.
If some disks are inaccessible at the time of a hostid opera‐
tion, you might need to use the voldisk clearimport operation to
clear out the old host ID on those disks when they become acces‐
sible. Otherwise, you might not be able to readd those disks to
their disk groups.
Note
Take care when using this command. If the system crashes before
the hostid operation completes, some disk groups might not reim‐
port automatically. Adds to the list of disks in the
/etc/vol/volboot file. Disks are specified based on their disk
access name. This name identifies the physical address of the
disk. For example, to add disk dsk3c, use the command:
/sbin/voldctl add disk dsk3c
If there is a disk access record in the rootdg configuration for
the named disk, configuration parameters are taken from that
record. Otherwise, you might need to specify some attributes to
voldctl add disk. Removes one or more disks from the
/etc/vol/volboot file. Disks are specified based on the name
used in the corresponding voldctl add disk operation. Lists the
contents of the /etc/vol/volboot file. This list includes the
host ID (which is usually the host name), some sequence numbers,
and the list of disks and disk attributes stored in the
/etc/vol/volboot file. Requests that vold enter enabled mode,
import all disk groups that were previously imported on this
host, and rebuild the volume device node directories. This oper‐
ation can be used even if vold is already in enabled mode, how‐
ever any deported disk groups remain deported. The primary pur‐
pose for using this operation when in enabled mode is to cause
vold to scan for any disks that were newly added since vold was
last started. This operation will also rebuild the volume
device nodes. In this manner, disks can be dynamically config‐
ured to the system and then recognized by the Logical Storage
Manager.
If this operation fails, voldctl exits with the appropriate
error status and displays an error message. Requests that vold
enter disabled mode. This might be necessary to perform some
maintenance operations. This does not disable any configuration
state loaded into the kernel. It only prevents further configu‐
ration changes to loaded disk groups until vold is reenabled.
Requests that vold exit. This might be necessary to reset the
Logical Storage Manager, such as using the -r reset option to
vold. This does not disable any configuration state loaded into
the kernel. It only affects the ability to make configuration
changes until vold is restarted. If the -k option is used vold
will be stopped by sending it a SIGKILL signal. The command will
delay for up to 1 second to verify that vold has exited. After 1
second if vold has not exited an error will be returned. Prints
the current operating mode of vold. The output format is:
mode: operating_mode
where operating_mode is either enabled, disabled, booted, or
not-running. With an argument of init, requests that vold
reread any persistently stored license information. If licenses
have expired, this might cause some features to become unavail‐
able. If new licenses have been added, this will make the fea‐
tures defined in those licenses available.
With no arguments, voldctl license prints the list of features
that are currently available based on known licensing informa‐
tion.
SEE ALSOvolintro(8), vold(8), voldg(8), voldisk(8), signal(4)voldctl(8)