When you delete a GAD pair, the GAD reserve attribute is assigned to one of the volumes (usually the S-VOL).
When you check a volume that has the reserve attribute using the raidcom get ldev command, the virtual LDEV ID (VIR_LDEV) is displayed as ffff.
- Delete the LU path to the volume that has the reserve attribute.
- If the DKCMAIN microcode version is A0-05-41 or later, check whether VSM auto-configuration is used on the operation-target volume.
If AUTO_VIRTUAL_STORAGE is YES, go to step 6. If AUTO_VIRTUAL_STORAGE is NO or if the DKCMAIN microcode version is earlier than A0-05-41, go to step 3.
raidcom get ldev –ldev_id 0x1111 –key virtual –fx –IH100 LDEV# VIR_LDEV Serial# V_Serial# V_ID V_NUMBER VOL_TYPE VIR_VOL_TYPE SSID VIR_SSID AUTO_VIRTUAL_STORAGE 4444 ffff 900061 911111 RH20ETP 1 OPEN-V-CVS - a - YES
-
Remove the reserve attribute.
Command example for removing the reserve attribute set for LDEV ID (0x4444):
raidcom unmap resource -ldev_id 0x4444 -virtual_ldev_id reserve
The volume from which the reserve attribute was removed changes to a volume whose virtual LDEV ID was deleted. If you use the raidcom get ldev command to check a volume whose virtual LDEV ID was deleted, the virutal LDEV ID (VIR_LDEV) is displayed as fffe.
-
Delete the virtual LDEV ID from the resource group.
Command example for deleting virtual LDEV ID (0x4444) from resource group (AnotherGroup), and then moving the virtual LDEV ID to meta_resource:
raidcom delete resource -resource_name AnotherGroup -ldev_id 0x4444
-
Set a virtual LDEV ID for the volume.
Command example for setting virtual LDEV ID (0x4444) for volume (0x4444):
raidcom map resource -ldev_id 0x4444 -virtual_ldev_id 0x4444
-
Delete the volume.
Command example:
raidcom delete ldev -ldev_id 0x4444 -operation initialize_capacity_saving
If VSM auto-configuration is used, you can also delete the volume with specifying the virtual information reset option (-virtual_info reset).
raidcom delete ldev -ldev_id 0x4444 -virtual_info reset -operation initialize_capacity_saving
Note: You need to set a unique virtual LDEV ID within the storage systems that use the volume. If the same virtual LDEV ID is used by another storage system or virtual storage machine that has the same serial number and model, the server cannot distinguish between volumes. In the worst-case scenario, the server detects inconsistencies.