Content-type: text/html
voldisksetup - Set up a disk for use with the Logical Storage Manager (LSM)
/usr/sbin/voldisksetup [option...] diskname [attribute...]
The voldisksetup command is normally called by the voldiskadd command as part of initial disk configuration. It should not normally be necessary to call this command directly.
The voldisksetup utility configures the disk for use by the Logical Storage Manager. Prior to calling voldisksetup, a valid disklabel should be installed on the disk.
The diskname argument directs the command to the disk being added. The diskname argument is a physical address, which is comprised of the following elements: the device mnemonic (rz for SCSI devices, re for EISA RAID devices, and ra for MSCP devices), the LUN for EISA RAID devices (l), the device unit number (n), and the partition identifier (p). The partition identifier is a lowercase letter in the range a to h. You omit the partition identifier to specify an entire disk and include the partition identifier to specify a particular partition on a disk. In other words, the format dd[l]n[nnn] identifies a SCSI disk and the format dd[l]n[nnn]p identifies a SCSI disk partition.
The -i option to voldisksetup causes a Logical Storage Manager initialization operation to be performed. The initialization operation adds a disk header and writes an empty configuration on the disk. This operation destroys any previous Logical Storage Manager database contents on the disk.
The -v option shows commands as they execute.
Valid
attribute
arguments are as follows:
This attribute represents the length of the public area (used
to create subdisks) to create on the disk. This defaults to the size of the
disk minus the private area on the disk.
This attribute represents the length of the private area (used
for Logical Storage Manager private data) to create on the disk. The default
for this area is 512 sectors.
This attribute causes no kernel logs or configuration databases
to be set up on the disk. The size of the private area is not changed, but
it will not contain the normal private data. This attribute is ignored unless
the
-i
option was supplied on the command line.
This attribute is the converse of the
noconfig
attribute and is the default. This attribute is ignored unless the
-i
option was supplied on the command line.
This attribute represents the number of configuration copies
to be initialized on the disk. The number of configuration copies should be
the same as the number of log copies. This defaults to 1.
This attribute represents the number of log copies to be initialized
on the disk. The number of log copies should be the same as the number of
configuration copies. This defaults to 1.
This attribute represents the length of each configuration
copy. The default values are calculated based on the values of
nconfig
and
nlog.
This attribute represents the length of each log copy. The
default values are calculated based on the values of
nconfig
and
nlog.
The
-F
and
-q
options to
voldisksetup
are used internally by the LSM utilities. The
-F
option is used to override partition overlap checks and the
-q
option is used to suppress overlap check messages. These options are for Digital
internal use only.
You may receive the following messages when using the voldisksetup command:
voldisk: Device special-device: Invalid attributes
This message indicates that invalid nconfig and nlog values were used to initialize the disk. The values used for nconfig and nlog must be the same. Initializing a disk with an nconfig value of 0 and the default nlog value of 1 can cause this error.
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 file system, 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 voldisksetup 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 voldisksetup will be marked as in use by LSM and all overlapping partitions will be marked UNUSED.
The following examples illustrate these messages: Initializing a LSM disk on a partition that is open and actively in use: # /usr/sbin/voldisksetup -i rz11c
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): # /usr/sbin/voldisksetup -i rz11
/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
disklabel(8), volintro(8), voldisk(8), voldiskadd(8)