When you add a disk drive to a diskset, Solstice DiskSuite/Solaris Volume Manager repartitions it as follows so that the state database for the diskset can be placed on the drive.
A small portion of each drive is reserved in slice 7 for use by Solstice DiskSuite/Solaris Volume Manager software. The remainder of the space on each drive is placed into slice 0.
Drives are repartitioned when they are added to the diskset only if slice 7 is not set up correctly.
Any existing data on the disks is lost by the repartitioning.
If slice 7 starts at cylinder 0, and the disk is large enough to contain a state database replica, the disk is not repartitioned.
Become superuser on the node.
Ensure that the diskset has been created.
For instructions, see How to Create a Diskset.
List the device ID (DID) mappings.
# scdidadm -L |
Choose drives that are shared by the cluster nodes that will master or potentially master the diskset.
Use the full DID pseudo-driver names when you add drives to a diskset.
The first column of output is the DID instance number, the second column is the full path (physical path), and the third column is the full DID pseudo-driver name (pseudo path). A shared drive has more than one entry for the same DID instance number.
In the following example, the entries for DID instance number 2 indicate a drive that is shared by phys-schost-1 and phys-schost-2, and the full DID name is /dev/did/rdsk/d2.
1 phys-schost-1:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1 2 phys-schost-1:/dev/rdsk/c1t1d0 /dev/did/rdsk/d2 2 phys-schost-2:/dev/rdsk/c1t1d0 /dev/did/rdsk/d2 3 phys-schost-1:/dev/rdsk/c1t2d0 /dev/did/rdsk/d3 3 phys-schost-2:/dev/rdsk/c1t2d0 /dev/did/rdsk/d3 ... |
Take ownership of the diskset.
# metaset -s setname -t |
Specifies the diskset name
Takes ownership of the diskset
Add the drives to the diskset.
Use the full DID pseudo-driver name.
# metaset -s setname -a DIDname |
Adds the disk drive to the diskset
Device ID (DID) name of the shared disk
Do not use the lower-level device name (cNtXdY) when you add a drive to a diskset. Because the lower-level device name is a local name and not unique throughout the cluster, using this name might prevent the metaset from being able to switch over.
Verify the status of the diskset and drives.
# metaset -s setname |
Do you intend to repartition drives for use in metadevices or volumes?
If yes, go to How to Repartition Drives in a Diskset.
If no, go to How to Create an md.tab File to define metadevices or volumes by using an md.tab file.
The metaset command adds the disk drives /dev/did/dsk/d1 and /dev/did/dsk/d2 to the diskset dg-schost-1.
# metaset -s dg-schost-1 -a /dev/did/dsk/d1 /dev/did/dsk/d2 |