Content-type: text/html Man page of voldctl


Section: Maintenance Commands (8)
Index Return to Main Contents


voldctl - Control the volume configuration daemon  


/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



The voldctl utility manages some aspects of the state of the volume configuration daemon, vold, and manages configuration aspects related to bootstrapping the rootdg disk group configuration.

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 that is used by the Logical Storage Manager 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 also contains a list of disks to scan in search of the rootdg disk group. At least one disk in this 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 /etc/vol/volboot file is stored in a system-dependent location. On systems that have usable NVRAM for storing configuration parameters, the volboot file may be stored in NVRAM. On other systems, the /etc/vol/volboot file is usually stored on the root file system in the /etc/vol directory.

vold operates in one of three modes: enabled, disabled, or booted. The enabled state is the normal operating state. Most configuration operations are allowed in the enabled state. Entering the enabled state imports all disk groups, and begins the management of device nodes stored in the /dev/vol, /dev/rvol, and /dev/plex directories.

In the disabled state, vold does not retain configuration information for the imported disk groups, and does not maintain the volume and plex device directories. Most operations are disallowed in the disabled state. Certain 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 action performed by voldctl depends upon the keyword specified as the first operand. Supported operations are: Reinitialize the /etc/vol/volboot file with a new host ID, and with an empty list of disks. If a hostid operand is specified, then this string is used; otherwise, a default host ID is used. The default host ID is normally taken as the network node name for the host (see uname(1)). On systems with a hardware-defined system ID, the default host ID might be derived from this hardware ID. Change the host ID in the /etc/vol/volboot file and on all disks in disk groups currently imported on this machine. It may be desirable 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 operation, it may be necessary to use the voldisk clearimport operation to clear out the old host ID on those disks when they become reaccessible. Otherwise, you may not be able to re-add those disks to their disk groups.
Take care when using this command. If the system crashes before the hostid operation completes, some disk groups may not reimport automatically. Add 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 rz3c, you might use the command:
/sbin/voldctl add disk rz3c
If there is a disk access record in the rootdg configuration for the named disk, then configuration parameters are taken from that record. Otherwise, it may be necessary to specify some attributes to /sbin/voldctl add disk. Remove one or more disks from the /etc/vol/volboot file. Disks are specified based on the name used in the corresponding /sbin/voldctl add disk operation. List the contents of the /etc/vol/volboot file. This list includes the host ID, some sequence numbers, and the list of disks and disk attributes stored in the /etc/vol/volboot file. Request that vold enter enabled mode, import all disk groups, and rebuild the volume and plex device node directories. This operation can be used even if vold is already in enabled mode. The primary purpose for using this operation when in enabled mode is to rebuild the volume and plex device nodes. This operation will also cause vold to scan for any disks that were newly added since vold was last started. In this manner, disks can be dynamically configured to the system and then recognized by the Logical Storage Manager. Request that vold enter disabled mode. This may be necessary to perform some maintenance operations. This does not disable any configuration state loaded into the kernel. It only prevents further configuration changes to loaded disk groups until vold is re-enabled. Request that vold exit. This may 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. Print the current operating mode of vold. The output format is:
mode: operating_mode
The variable operating_mode is either enabled, disabled, booted, or not-running.


volintro(8), vold(8), voldg(8), voldisk(8)




This document was created by man2html, using the manual pages.
Time: 02:40:29 GMT, October 02, 2010