>>- svctask -- -- chvdisk -- -----------------------------------> >--+---------------------------------------------+--------------> '- -iogrp --+- io_group_id ---+--+----------+-' '- io_group_name -' '- -force -' >--+-----------------------------------------+------------------> '- -rate -- throttle_rate --+-----------+-' '- -unitmb -' >--+-------------------------+--+- vdisk_name -+--------------->< '- -name -- new_name_arg -' '- vdisk_id ---'
| Note: The -iogrp, -rate, and -name parameters are mutually exclusive. Only one of these parameters can be specified per command-line. |
This command modifies a single property of a virtual disk. You can modify one property at a time. Therefore, to change the name and modify the I/O group, you must issue the command twice.
You can specify a new name or label. You can use the new name subsequently to refer to the virtual disk.
You can change the I/O group with which this virtual disk is associated. However, to change the I/O group, you must first flush the cache within the nodes in the current I/O group to ensure that all data is written to disk. You should suspend I/O operations at the host level before performing this operation.
| Attention: Do not move a VDisk to an offline I/O group. You must ensure the I/O group is online before moving the VDisks to avoid any data loss scenarios. |
You can set a limit on the amount of I/O transactions that will be accepted for this virtual disk. It is set in terms of I/Os per second or MBps. By default, no I/O governing rate is set when a virtual disk is created.
When first created there is no throttling applied to a virtual disk. Using the -rate parameter can change this. To change the virtual disk back to an unthrottled state, the value 0 (zero) should be used with the -rate parameter.
You can migrate a VDisk to a new I/O group to manually balance the workload across the nodes in the cluster. You may end up with a pair of nodes that are overworked and another pair that are underworked. Follow this procedure to migrate a single VDisk to a new I/O group. Repeat for other VDisks as required.
| Attention: |
Before migrating the VDisk, it is essential that for each vpath presented by the VDisk you intend to move, the SDD configuration is updated to remove the vpaths in question. Failure to do this may result in data corruption. See IBM TotalStorage Subsystem Device Driver: User's Guide for details about how to dynamically reconfigure SDD for the given host operating system.
Make sure that when you migrate a VDisk to a new I/O group, you quiesce all I/O operations for the VDisk. You may need to determine the hosts that are using this VDisk. Any FlashCopy mappings or Remote Copy relationships that use this VDisk should be stopped or deleted. Issue the following command, to check if the VDisk is part of a relationship or mapping, issue the svcinfo lsvdisk <vdiskname/id> command, where <vdiskname/id> is the name or ID of the VDisk.
Look for the FC_id and RC_id fields.
If these are not blank then the VDisk is part of a mapping or relationship.
See the IBM TotalStorage SAN Volume Controller: Command-Line Interface User's Guide for details on how to stop or delete
the mapping or relationship. Issue the following command to migrate the VDisk:
svctask chvdisk -iogrp <newiogrpname/id> <vdiskname/id>
Follow
the procedure to discover the new vpaths and to check that each vpath is now
presenting the correct number of paths. See the IBM TotalStorage Subsystem Device Driver: User's Guide for details
on how to dynamically reconfigure SDD for the given host operating system.
An invocation example
svctask chvdisk -rate 2040 -unit mb 6
The resulting output
No feedback