Creating Disk Sets

How to Create a Disk Set

Before You Begin

Check Guidelines for Working With Disk Sets.

1. To create a disk set, use one of the following methods:

   • From the Enhanced Storage tool within the Solaris Management Console, open the Disk Sets node. Choose Action⇒Create Disk Set. Then, follow the instructions in the wizard. For more information, see the online help.

   • To create a disk set from scratch from the command line, use the following form of the metaset command:

     # metaset -s diskset-name -a -h -M hostname

     -s diskset-name

     Specifies the name of a disk set on which the metaset command will work.

     -a

     Adds hosts to the named disk set. Solaris Volume Manager supports up to four hosts per disk set.

     -M

     Specifies that the disk set being created is a multi-owner disk set.

     -h hostname

     Specifies one or more hosts to be added to a disk set. Adding the first host creates the set. The second host can be added later. However, the second host is not accepted if all the disks within the set cannot be found on the specified hostname. hostname is the same name found in the /etc/nodename file.

     See the metaset(1M) man page for more information.

2. Check the status of the new disk set.

   # metaset

Example 19-1 Creating a Disk Set

In the following example, you create a shared disk set called blue, from the host host1. The metaset command shows the status. At this point, the disk set has no owner. The host that adds disks to the set becomes the owner by default.

# metaset -s blue -a -h host1              
# metaset
Set name = blue, Set number = 1

Host                Owner
  host1                

Example 19-2 Creating a Multi-Owner Disk Set

In the following example, you create a multi-owner disk set called red. The first line of the output from the metaset command displays “Multi-owner,” indicating that the disk set is a multi-owner disk set.

# metaset -s red -a -M -h nodeone
# metaset -s red
Multi-owner Set name = red, Set number = 1, Master = 

Host                Owner          Member
  nodeone                          Yes