Block Storage

 View Only

  • 1.  RAIDCOM - GAD Pair delete forced

    Posted 05-23-2023 08:22
    Edited by System 10-17-2025 15:02

    Hello,

    I can't delete the LUN path because it is the last path of remote copy.

    The status of the GAD Pair looks like :

    raidscan -p CL5-B-2  -fx -l 2 -CLI -I50
PORT# /ALPA/C TID#  LU# Seq#   Num  LDEV# P/S  Status Fence  P-Seq# P-LDEV#
CL5-B-2  dc  0   0    2 480050     1   410 P-VOL PSUS  NEVER   480089    410


    The P-Vol is in PSUS and the the related S-Vol is 0x410 on #89.
    But the 0x410 on #89 does not any more exist.

    # raidcom get ldev -ldev_id 0x410  -fx  -I89
Serial#  : 480089
LDEV : 410 VIR_LDEV : ffff
SL : -
CL : -
VOL_TYPE : NOT DEFINED       
SSID : 0008
RSGID : 1


    The 0x410 was the old S-Vol that the reason why we see here VIR_LDEV : ffff.

    I've tried different pairsplit options, to do a forced GAD pair delete - but always it does not work.

    Any idea ? How to recover from this state ?

    regards
    Sven



    ------------------------------
    Sven Kirsten
    Systems Engineer
    SVA System Vertrieb Alexander GmbH
    ------------------------------


  • 2.  RE: RAIDCOM - GAD Pair delete forced

    Posted 05-24-2023 10:58
    Edited by System 10-17-2025 15:02

    Hi Sven,

    i would just resync the pair (creating LDEV for 410 in #89) and then delete it again.
    You can just delete it forcibly, when both volumes are in I/O Mode "blocked" as i know.

    Best regards

    Toni



    ------------------------------
    Antonius Schwefer
    Non-Hitachi Vantara
    ------------------------------



  • 3.  RE: RAIDCOM - GAD Pair delete forced

    Posted 05-26-2023 03:19
    Edited by System 10-17-2025 15:02

    Hallo Sven,  please post  raidcom get ldev -ldev id... for both p and s vols.
    But.. the pairsplit command will do it.


    To Split the pair removing the virtual_ldev_id from the SVOL.
    pairsplit -g gad00 -RF -l -IH1.
    pairdisplay -g gad00 -fcex -IH0  svol is now smplx  and gad reserved.

    Now Split the pair leaving  the virtual_ldev_id on the PVOL
    PVol is smplx  but has virtual ldev id and is still visible to hosts.
    pairsplit -g gad00 -SFV -l -IH0

    Now you can delete the paths to the SVOL and delete the SVOL
    svol ldev_id  no longer reserved

    -RF  make the Svol simplex , reserved  and no host access  no longer a GAD  in the vol_type
    -RFV  make the Svol simplex , still a GAD  in the vol_type, still has virt_ldev id and is accessible to hosts IO.
    -SF  make the Pvol simplex , reserved  and no host access  no longer a GAD  in the vol_type
    -SFV  make the Pvol simplex , still a GAD  in the vol_type, still has virt_ldev id and is accessible to hosts IO.












    ------------------------------
    Matt Muldoon
    Systems Engineer
    TD SYNNEX Germany GmbH & Co. OHG
    ------------------------------



  • 4.  RE: RAIDCOM - GAD Pair delete forced

    Posted 05-26-2023 03:22
    Edited by System 10-17-2025 15:02

    Hi again, remember to use the -l  (local) .. then you can address only the Svol or Pvol .. both storages do not have to be accessible to horcm.



    ------------------------------
    Matt Muldoon
    Systems Engineer
    TD SYNNEX Germany GmbH & Co. OHG
    ------------------------------

    Original Message


  • 5.  RE: RAIDCOM - GAD Pair delete forced

    Posted 05-30-2023 03:35
    Edited by System 10-17-2025 15:02

    Hi Sven, I have to correct that last part:
    -RF  make the Svol simplex , reserved  and no host access
    -RFV  make the Svol simplex . Still has virt_ldev id and is accessible to hosts IO.
    -SF  make the Pvol simplex , reserved  and no host access.
    -SFV  make the Pvol simplex. Still has virt_ldev id and is accessible to hosts IO.



    ------------------------------
    Matt Muldoon
    Systems Engineer
    TD SYNNEX Germany GmbH & Co. OHG
    ------------------------------

    Original Message