Perform this procedure to create disk sets.
Determine whether the cluster will have more than three disk sets after you create the new disk sets.
If the cluster will have no more than three disk sets, skip to Step 2.
If the cluster will have four or more disk sets, perform the following steps to prepare the cluster.
You must perform this task whether you are installing disk sets for the first time or whether you are adding more disk sets to a fully configured cluster.
On any node of the cluster, check the value of the md_nsets variable in the /kernel/drv/md.conf file.
If the total number of disk sets in the cluster will be greater than the existing value of md_nsets minus one, increase the value of md_nsets to the desired value.
The maximum permissible number of disk sets is one less than the configured value of md_nsets. The maximum possible value of md_nsets is 32, therefore the maximum permissible number of disk sets that you can create is 31.
Ensure that the /kernel/drv/md.conf file is identical on each node of the cluster.
Failure to follow this guideline can result in serious Solstice DiskSuite or Solaris Volume Manager errors and possible loss of data.
If you made changes to the md.conf file on any node, perform the following steps to make those changes active.
On each node in the cluster, run the devfsadm(1M) command.
You can run this command on all nodes in the cluster at the same time.
From one node of the cluster, run the scgdevs(1M) command to update the global-devices namespace.
The scgdevs command calls itself remotely on all nodes, even when the command is run from just one node. To determine whether the scgdevs command has completed processing, run the following command on each node of the cluster.
% ps -ef | grep scgdevs
Ensure that the disk set you intend to create meets one of the following requirements.
If the disk set is configured with exactly two disk strings, the disk set must connect to exactly two nodes and use exactly two mediator hosts. These mediator hosts must be the same two hosts used for the disk set. See Configuring Dual-String Mediators for details on how to configure dual-string mediators.
If the disk set is configured with more than two disk strings, ensure that for any two disk strings S1 and S2, the sum of the number of drives on those strings exceeds the number of drives on the third string S3. Stated as a formula, the requirement is that count(S1) + count(S2) > count(S3).
Ensure that the local state database replicas exist.
For instructions, see How to Create State Database Replicas.
Become superuser on the cluster node that will master the disk set.
Create the disk set.
The following command creates the disk set and registers the disk set as a Sun Cluster disk device group.
# metaset -s setname -a -h node1 node2
Specifies the disk set name
Adds (creates) the disk set
Specifies the name of the primary node to master the disk set
Specifies the name of the secondary node to master the disk set
When you run the metaset command to configure a Solstice DiskSuite or Solaris Volume Manager device group on a cluster, the command designates one secondary node by default. You can change the desired number of secondary nodes in the device group by using the scsetup(1M) utility after the device group is created. Refer to “Administering Disk Device Groups” in Sun Cluster System Administration Guide for Solaris OS for more information about how to change the numsecondaries property.
Verify the status of the new disk set.
# metaset -s setname
Add drives to the disk set.
Go to Adding Drives to a Disk Set.
The following command creates two disk sets, 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