createvsd – Creates a set of virtual shared disks, with their associated logical volumes.
Use this command to create a volume group with the specified name (if one does not already exist) and to create a logical volume within that volume group. You specify the logical volume size using the -s flag.
You can use the System Management Interface Tool (SMIT) to run this command. To use SMIT, enter:
smit vsd_dataand select the Create a virtual shared disk option.
[P/S] : disk_list1+disk_list2/[S1/S2/...Sn] : disk_list1+disk_list2/createvsd -n 1,6,4 -v PRETo create a volume group that spans hdisk2, hdisk3, and hdisk4 on node 1, with a backup on node 3, enter:
createvsd -n 1/3:hdisk2,hdisk3,hdisk4/ -v DATATo create volume groups just like that one on nodes 1, 2, and 3 of a system with backup on nodes 4, 5, and 6 of the same system, enter:
createvsd -n 1/4:hdisk1,hdisk2,hdisk3/,2/5:hdisk5,hdisk6, \
          hdisk7/,3/6:hdisk2,hdisk4,hdisk6/ -v DATAThis command is shown on two lines here, but you must enter it without any spaces between the items in node_list.
To create a virtual shared disk where the logical volume spans only two of the physical disks in the volume group, enter:
createvsd -n 1/3:hdisk1,hdisk2+hdisk3/ -v DATAThis command creates the virtual shared disk DATA1n1 with logical volume lvDATA1n1 spanning hdisk1 and hdisk2 in the volume group DATA, which includes hdisk1, hdisk2, and hdisk3. It exports the volume group DATA to node 3.
If a volume group is already created and the combined physical hdisk lists contain disks that are not needed for the logical volume, those hdisks are added to the volume group. If the volume group has not already been created, createvsd creates a volume group that spans hdisk_list1+hdisk_list2.
Backup nodes cannot use the same physical disk as the primary does to serve virtual shared disks.
ALL specifies that you are creating virtual shared disks on all nodes in the RSCT peer domain. No backup nodes are assigned if you use this operand. The virtual shared disks will be created on all the physical disks attached to the nodes in node_list (you cannot specify which physical disks to use.)
createvsd -n 6 -g VSDVGcreatevsd -n 6/3/ -g VSDVGcreatevsd -n 1,6 -c 2 -v DATAcreatevsd -n 1,6 -c 2 -A DATAcreatevsd -n 1 -v DATAcreatevsd -n 1 -v DATA -l newIt is usually more helpful not to specify -l, so that your lists of virtual shared disk names and logical volume names are easy to associate with each other and you avoid naming conflicts.
The Logical Volume Manager limits the number of physical partitions to 1016 per disk. If a disk is greater than 4 gigabytes in size, the physical partition size must be greater than 4MB to keep the number of partitions under the limit.
is not done as part of the createvsd processing. This speeds the operation of the command and avoids unnecessary processing in the case where several virtual shared disks are being created on the same primary/secondary nodes. In this case, however, you should either not specify -x on the last createvsd in the sequence or issue the volume group commands listed above explicitly.
None.
You must have root authority to run this command.
You must issue this command from a node that is online in the peer domain. To bring a peer domain online, use the startrpdomain command. To bring a particular node online in an existing peer domain, use the startrpnode command. For more information on creating and administering an RSCT peer domain, refer to the RSCT: Administration Guide.
For the following command:
createvsd -n 1/2:hdisk13/ -s 1024 -g testvg -v testvsd -T 16The messages to standard output will be similar to:
createvsd: calls Getopts.
createvsd: parsing node_list.
createvsd: creates task tables.
createvsd: calls checkclvm.perl on the nodes c164n11.ppd.pok.ibm.com
createvsd: calls domkvglv.perl.
OK:1:mkvg -f -y testvg -s 16 hdisk13
OK:1:mklv -a c -y lvtestvsd1n1 -e x testvg 64 hdisk13
It took about 8 seconds in mkvglv.
createvsd: calls dovaryoffvg.perl testvg on the primary node c164n11.ppd.pok.ibm.com
OK:1:chvg -a n testvg
OK:1:varyoffvg testvg
createvsd: calls doimportvg.perl testvg on the nodes c164n12.ppd.pok.ibm.com with 000048186b991a6f
importvg : testvg
importvg : OK:2:importvg -y testvg hdisk5
importvg : OK:2:chvg -a n testvg
importvg : timestamp 2 testvg 3e036cb33403c8c8
importvg : OK:2:varyoffvg testvg
importvg : It took about 10 seconds.
It took about 12 seconds in importvg.
createvsd: calls vsdvg.
OK:1:vsdvg -g testvgn1b2 testvg 1 2
It took about 12 seconds in vsdvg.
createvsd: calls dovaryonvg.perl testvg on pri nodes c164n11.ppd.pok.ibm.com
OK:1:varyonvg  testvg
createvsd: calls defvsd.
OK:1:defvsd lvtestvsd1n1 testvgn1b2 testvsd1n1
It took about 5 seconds in defvsd.   To create two 4MB virtual shared disks on each of three primary nodes, one of which has a backup, enter:
createvsd -n 3,4,7/8/ -c 2 -s 4 -g vsdvg -v TEMPThis command creates the following virtual shared disks:
To create three virtual shared disks, where the logical volume created on node 3 spans fewer disks than the volume group does, enter:
createvsd -n 3,4/:hdisk1,hdisk2+hdisk3/,7/8/ -s 4 -g datavg -v USER/opt/rsct/vsd/bin/createvsd