Reusing a volume that was an S-VOL

Global Active Device for VSP One Block

Version
10.5.x
File Size
25537 KB
Audience
anonymous
Part Number
MK-23VSP1B011-11
ft:lastEdition
2026-06-23

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.

  1. Delete the LU path to the volume that has the reserve attribute.
  2. 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 3. If AUTO_VIRTUAL_STORAGE is NO or if the DKCMAIN microcode version is earlier than A0-05-41, go to step 4.

    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
  3. Reset the virtual information of the volume (-virtual_info reset_and_delete_ldev_id).

    After the operation is complete, go to step 5.

    raidcom modify ldev -virtual_info reset_and_delete_ldev_id -ldev_id 0x4444 -request_id auto -IH1
  4. 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 virtual LDEV ID (VIR_LDEV) is displayed as fffe.

  5. Reserve an LDEV ID for the resource group that will use the volume.

    Command example for reserving LDEV ID (0x4444) for resource group (#0):

    raidcom add resource -resource_name meta_resource -ldev_id 0x4444
  6. Set a virtual LDEV ID for the volume.
    Note: You must set a virtual LDEV ID that is unique within the storage system that uses the volume. If the same virtual LDEV ID is used in other storage systems or virtual storage machines with the same serial number and model, identification of multiple volumes with the same virtual LDEV ID might cause problems. At worst, the server might detect an inconsistency.

    Command example for setting virtual LDEV ID (0x5555) for volume (0x4444):

    raidcom map resource -ldev_id 0x4444 -virtual_ldev_id 0x5555
  7. Specify a new port and host group for the volume, and set an LU path to the volume.