volsetup - Initialize the Logical Storage Manager (LSM) by creating rootdg disk group.
/usr/sbin/volsetup [-o force] [-n num] [diskname|partition...]
The volsetup script should be run after installing the LSM kit. volsetup is an interactive script which prompts for a disk name, if one is not provided on the command line. If the complete disk cannot be added to LSM, partition names can also be given.
If more than one disk name or partition name is given as input, all the disks and partitions are added to the rootdg disk group.
The -n num option can be used to specify an estimate of the number of disks that will be in the rootdg disk group. volsetup uses the value specified by the num parameter to create a private region of appropriate size and to select an optimal number of configuration copies per disk.
The -o force option can be used to remove an existing LSM configuration and reinitialize LSM.
voliods by default. After running
is fully functional.
You may receive the following messages when using the volsetup command. LSM initialization will fail if none of the disks specified can be initialized into LSM.
A previous LSM configuration exists (err=22). Use the "-o force" option to reinitialize LSM. Stop.
This message indicates that LSM has already been initialized on the system. To reinitialize LSM, use the -o force option. This will remove any previous LSM configuration.
special-device or an overlapping partition is open Quitting...
This message indicates that you tried to initialize an LSM disk on a partition or a disk that is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device.
special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data CONTINUE? [y/n]
This message indicates that you tried to initialize an LSM disk on a partition that is not currently in active use but is marked for use in the disk label's partition map. For example, the partition may be part of a UFS filesystem (4.2BSD) or an AdvFS domain.
If you know that the partition you specified to volsetup does not contain any data, you can choose to override the warning. In this case, the fstype in the disk label will be modified to an LSM fstype such as LSMsimp, LSMpubl or LSMpriv. The exact fstype depends on whether a disk or a partition is given as an argument to voldisksetup.
Note that you can use the command disklabel -s to set the fstype in the disk label to unused for partitions that do not contain any valid data. See disklabel(8) for more information.
Partition(s) which overlap special-device are marked in use. If you continue with the operation you can possibly destroy existing data. CONTINUE? [y/n]
This message indicates that the partition you specified is not marked for use, but other, overlapping partitions on the disk are marked for use. If you override this warning, the fstype in the disk's label will be modified. The partition you specified to volsetup will be marked as in use by LSM and all overlapping partitions will be marked UNUSED.
The following examples illustrate these messages: Initializing an LSM disk on a partition that is open and actively in use:
rz11c or an overlapping partition is open. Quitting... Initializing an LSM sliced disk on a disk which has partition g marked for use by UFS (4.2BSD):
/dev/rrz11g is marked in use for 4.2BSD in the disklabel. If you continue with the operation you can possibly destroy existing data. CONTINUE? [y/n]
Partition(s) which overlap /dev/rrz11c are marked in use. If you continue with the operation you can possibly destroy existing data. CONTINUE? [y/n]
The disklabel for rz11 does not exist or is corrupted. Quitting...
The following is an example of volsetup usage :
# /usr/sbin/volsetup rz3 rz8h
This will add disk
Commands: disklabel(8), volintro(8), vold(8), voliod(8)
Guide: Logical Storage Manager