Example--Creating a Diskset
The following command creates two disksets, dg-schost-1 and dg-schost-2, with the nodes phys-schost-1 and phys-schost-2 specified as the potential primaries.
# metaset -s dg-schost-1 -a -h phys-schost-1 phys-schost-2 # metaset -s dg-schost-2 -a -h phys-schost-1 phys-schost-2 |
Adding Disk Drives to a Diskset
When you add a disk drive to a diskset, Solstice DiskSuite/Solaris Volume Manager repartitions the disk drive as follows so that the state database for the diskset can be placed on the disk drive.
A small portion of each disk drive is reserved in slice 7 for use by Solstice DiskSuite/Solaris Volume Manager software. The remainder of the space on each disk drive is placed into slice 0.
Disk drives are repartitioned when they are added to the diskset only if slice 7 is not configured correctly.
Any existing data on the disk drives is lost by the repartitioning.
If slice 7 starts at cylinder 0, and the disk drive partition is large enough to contain a state database replica, the disk drive is not repartitioned.
How to Add Disk Drives to a Diskset
Become superuser on the node.
Ensure that the diskset has been created.
For instructions, see How to Create a Diskset.
List the DID mappings.
# scdidadm -L
Choose disk drives that are shared by the cluster nodes that will master or potentially master the diskset.
Use the full device-ID path names when you add disk drives to a diskset.
The first column of output is the DID instance number, the second column is the full physical path name, and the third column is the full device-ID path name (pseudo path). A shared disk 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 disk drive that is shared by phys-schost-1 and phys-schost-2, and the full device-ID path 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
-s setname Specifies the diskset name
-t Takes ownership of the diskset
Add the disk drives to the diskset.
Use the full device-ID path name.
# metaset -s setname -a drivename
-a Adds the disk drive to the diskset
drivename Full device-ID path name of the shared disk drive
Note - Do not use the lower-level device name (cNtXdY) when you add a disk 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 disk drives.
# metaset -s setname
Do you intend to repartition disk drives for use in metadevices or volumes?
If yes, go to How to Repartition Disk 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.
Example--Adding Disk Drives to a Diskset
The metaset command adds the disk drives /dev/did/rdsk/d1 and /dev/did/rdsk/d2 to the diskset dg-schost-1.
# metaset -s dg-schost-1 -a /dev/did/rdsk/d1 /dev/did/rdsk/d2 |
How to Repartition Disk Drives in a Diskset
The metaset(1M) command repartitions disk drives in a diskset so that a small portion of each disk drive is reserved in slice 7 for use by Solstice DiskSuite/Solaris Volume Manager software. The remainder of the space on each disk drive is placed into slice 0. To make more effective use of the disk drive, use this procedure to modify the disk layout. If you allocate space to slices 1 through 6, you can use these slices when you set up Solstice DiskSuite metadevices or Solaris Volume Manager volumes.
Become superuser on the cluster node.
Use the format command to change the disk partitioning for each disk drive in the diskset.
When you repartition a disk drive, you must meet the following conditions to prevent the metaset(1M) command from repartitioning the disk drive.
Create slice 7 starting at cylinder 0, large enough to hold a state database replica (approximately 2 Mbytes).
Set the Flag field in slice 7 to wu (read-write, unmountable). Do not set it to read-only.
Do not allow slice 7 to overlap any other slice on the disk drive.
See the format(1M) man page for details.
Define metadevices or volumes by using an md.tab file.
Go to How to Create an md.tab File.