# raidcom get ldev -ldev_id 200
While the delete LDEV operation is in process, the VOL_TYPE is
REMOVING. When the volume is deleted correctly, the VOL_TYPE changes
from REMOVING to NOT DEFINED.
If VOL_TYPE is other than REMOVING or NOT DEFINED, the deletion
ended abnormally. Check CSV_Status to take either of the following
actions:
¢
When CSV_Status shows FAILED, see the Troubleshooting Dynamic
Provisioning section in the Provisioning Guide for your system.
¢
When CSV_Status shows a status other than FAILED or does not show
any status, execute the raidcom delete ldev command again without
specifying the -operation initialize_capacity_saving option.
Deleting a virtual volume by blocking, initializing, and then deleting the volume
Use the following procedure to delete a virtual volume by blocking,
initializing, and then deleting the volume. The command examples in this
procedure use LDEV number 200 for the virtual volume being deleted.
1
.
Block the volume by executing the
raidcom modify ldev
command.
# raidcom modify ldev -status blk –ldev_id 200
2
.
Verify that the block LDEV command completed normally by executing the
raidcom get command_status
command. If the command completed
normally, the value “0” is returned.
# raidcom get command_status
3
.
Initialize the volume by executing the
raidcom initialize ldev
command.
# raidcom initialize ldev -operation fmt -ldev_id 200
4
.
Verify that the initialize LDEV command completed normally by executing
the
raidcom get command_status
command. If the command completed
normally, the value “0” is returned.
# raidcom get command_status
5
.
Check the status of the volume by executing the
raidcom get ldev
command.
# raidcom get ldev -ldev_id 200
When the volume is initialized correctly, the VOL_TYPE is OPEN-V-CVS
and the CSV_Status is DISABLED.
6
.
Delete the volume by executing the
raidcom delete ldev
command.
# raidcom delete ldev -ldev_id 200
7
.
Verify that the delete LDEV command completed normally by executing
the
raidcom get command_status
command. If the command completed
normally, the value “0” is returned.
# raidcom get command_status
5-32
Provisioning operations with CCI
Command Control Interface User and Reference Guide
Содержание HUS VM
Страница 10: ...x Command Control Interface User and Reference Guide ...
Страница 18: ...xviii Preface Command Control Interface User and Reference Guide ...
Страница 78: ...2 50 CCI software environment Command Control Interface User and Reference Guide ...
Страница 154: ...4 8 Starting up CCI Command Control Interface User and Reference Guide ...
Страница 191: ...Provisioning operations with CCI 5 37 Command Control Interface User and Reference Guide ...
Страница 277: ... 1 UR 2x2 Data replication operations with CCI 6 53 Command Control Interface User and Reference Guide ...
Страница 280: ...6 56 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Страница 286: ...6 62 Data replication operations with CCI Command Control Interface User and Reference Guide ...
Страница 302: ...7 16 Data protection operations with CCI Command Control Interface User and Reference Guide ...
Страница 324: ...8 22 Examples of using CCI commands Command Control Interface User and Reference Guide ...
Страница 524: ...9 200 Troubleshooting Command Control Interface User and Reference Guide ...
Страница 529: ...Command Control Interface User and Reference Guide ...