 |
Index for
Section 8 |
|
 |
Alphabetical
listing for V |
|
 |
Bottom of
page |
|
volsetup(8)
NAME
volsetup, lsmsetup - Initializes Logical Storage Manager (LSM) by creating
the rootdg disk group
SYNOPSIS
/usr/sbin/volsetup [-c] [-o force] [-n num] [-s] [diskname | partition...]
[attribute...]
OPTIONS
The following options are recognized:
-c Clears the lock protecting multiple nodes in a cluster from
simultaneously running the volsetup command. After clearing the lock,
it is taken out on behalf of the initiating node.
-n num
Specifies the approximate number of disks to be managed by LSM. This
option is currently ignored and is only provided for compatibility with
existing scripts.
-o force
Forces re-initialization if LSM has already been initialized.
-s Synchronizes a node with cluster members.
DESCRIPTION
The volsetup script is an interactive script that should be run after
installing LSM. The diskname or partition parameter specifies the name of
at least one disk or partition to be used in creating the rootdg disk
group. If no disk or partition name is given on the command line, the
volsetup script prompts for this information.
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 -o force option can be used to remove an existing LSM configuration and
reinitialize LSM.
The volsetup script starts the vold daemon and one voliod daemon per CPU by
default. After volsetup has been run, LSM is fully functional.
To configure LSM in a TruCluster Version 5.0 multi-member cluster, run the
volsetup command from one of the cluster members and run the volsetup -s on
the other cluster members. If additional members are later added to the
cluster with the clu_add_member utility, do not run volsetup -s command on
the new member. The clu_add_member utility automatically synchronizes LSM
on the new node.
ATTRIBUTES
The following attributes can be specified to affect the layout strategy
used by volsetup:
publen=length
Specifies the length of the public area to create on the disk. This
defaults to the size of the disk minus the private area on the disk.
privlen=length
Specifies the length of the private area to create on the disk. The
default is 4096 sectors.
nconfig=number
Specifies the number of configuration copies and log copies to be
initialized on the disk. The number of configuration copies will be the
same as the number of log copies. This defaults to 1.
configlen=length
Specifies the length in sectors of each configuration copy. The
default values are calculated based on the value of nconfig.
loglen=length
Specifies the length in sectors of each log copy. The default values
are calculated based on the value of nconfig.
comment=string
Specifies a user-defined comment.
ERRORS
You may receive the following messages when using the volsetup command. LSM
initialization fails if none of the disks specified can be initialized by
LSM.
The following message indicates that LSM is initialized on the system. To
reinitialize LSM, use the -o force option, which removes previous LSM
configuration.
A previous LSM configuration exists (err=22).
Use the "-o force" option to reinitialize LSM.
Stop.
The following message indicates that you tried to initialize an LSM disk on
a partition or on a disk that is actively in use. The partition could be a
mounted UFS or AdvFS filesystem that is initialized as an LSM disk or used
as a swap device.
special-device or an overlapping partition is open.
The following 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.
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]
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 is 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.
The following message indicates that the partition you specified is not
marked for use, but other, overlapping partitions on the disk are marked
for use.
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]
If you override this warning, the fstype in the disk's label is 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:
1. Initializing an LSM disk on a partition that is open and actively in
use:
# /usr/sbin/volsetup dsk11c
dsk11c or an overlapping partition is open.
2. Initializing an LSM sliced disk on a disk which has partition g marked
for use by UFS (4.2BSD):
# /usr/sbin/volsetup dsk11
/dev/rdisk/dsk11g 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 g of disk dsk11 is marked for use by UFS (4.2BSD). If UFS is
not actively using this partition and the partition does not contain
any data, you may want to override this warning, by answering y. In
this case, partition g will be marked as LSMpubl and partition h will
be marked as LSMpriv in the disk label.
3. Initializing an LSM simple disk on a partition whose overlapping
partitions are marked for use:
# /usr/sbin/volsetup dsk11c
Partition(s) which overlap /dev/rdisk/dsk11c are marked in use.
If you continue with the operation you can possibly destroy
existing data.
CONTINUE? [y/n]
Partition c, which is being initialized into LSM, is not currently in
use, but other partition(s) which overlap with partition c are marked
in use in the disk label. If you answer y, partition c on disk dsk11
will be marked LSMsimp in the disk label and all partitions that
overlap partition c will be marked UNUSED.
4. Initializing an LSM disk on a disk that has no disk label:
# /usr/sbin/volsetup dsk11
The disklabel for dsk11 does not exist or is corrupted.
Quitting...
See disklabel(8) for information on installing a disk label on a disk.
EXAMPLES
The following is an example of volsetup usage :
# /usr/sbin/volsetup dsk3 dsk8h
This will add disk dsk3 and partition dsk8h to the rootdg disk group.
SEE ALSO
disklabel(8), volintro(8), vold(8), voliod(8)
|
Index for
Section 8 |
|
|
Alphabetical
listing for V |
|
 |
Top of
page |
|