Hello Miran,
I'm sure one of you wonderful Global Delivery folks you've worked with could assist in this conversation, but I'm unable to tag them here for awareness.
What they would tell you is that filesystems are no shrinkable and thus neither is a span.
Below is an example of what I mean - there is a single span with 32 SD's and multiple filesystems. One cannot 'remove' any SD's, this is fundamentally impossible.
- unmount all filesystems
- delete all filesystems
- recycle all filesystems
- unmap all vacated chunks on span (this could take time) as this returns space to the HDP pool
- delete span
- deny access to all SD's
- using Storage Navigator, unmap LUNs from all ports
- forget the SD's
I wager this is not what you would like to do.
<span-list -fsv for pnode 2>
Span instance name OK? Free Cap/GiB Chunks Con Snap Cod fullness Cluster Permanent ID DWB HDP free
--------------------- --- ---- ------- --------------------- --- ---- -------------- ------- ---------------- --- --------
NAS_OBR_DL Yes 56% 166400 9244 x 19327352832 90% 7%, 12%, 19% This 2BCB92CD790C15DB Yes 1330509
On HDP pool 0 with 1330509GiB free, shared with NAS_ORA_DL and NAS_SQL_DL
Set 0: 32 x 5200GiB = 166400GiB, of which 94454GiB is free, 0GiB is vacated, 94454GiB is available
SD 128 (rack '448664', SD '0B00')
SD 129 (rack '448664', SD '0B01')
SD 130 (rack '448664', SD '0B02')
SD 131 (rack '448664', SD '0B03')
SD 132 (rack '448664', SD '0B04')
SD 133 (rack '448664', SD '0B05')
SD 134 (rack '448664', SD '0B06')
SD 135 (rack '448664', SD '0B07')
SD 136 (rack '448664', SD '0B08')
SD 137 (rack '448664', SD '0B09')
SD 138 (rack '448664', SD '0B0A')
SD 139 (rack '448664', SD '0B0B')
SD 140 (rack '448664', SD '0B0C')
SD 141 (rack '448664', SD '0B0D')
SD 142 (rack '448664', SD '0B0E')
SD 143 (rack '448664', SD '0B0F')
SD 144 (rack '448664', SD '0B10')
SD 145 (rack '448664', SD '0B11')
SD 146 (rack '448664', SD '0B12')
SD 147 (rack '448664', SD '0B13')
SD 148 (rack '448664', SD '0B14')
SD 149 (rack '448664', SD '0B15')
SD 150 (rack '448664', SD '0B16')
SD 151 (rack '448664', SD '0B17')
SD 152 (rack '448664', SD '0B18')
SD 153 (rack '448664', SD '0B19')
SD 154 (rack '448664', SD '0B1A')
SD 155 (rack '448664', SD '0B1B')
SD 156 (rack '448664', SD '0B1C')
SD 157 (rack '448664', SD '0B1D')
SD 158 (rack '448664', SD '0B1E')
SD 159 (rack '448664', SD '0B1F')
fs LNZFS01_3banken_1 RepTg, EVS 1, cap 10224, con 10240 , perm 2BCB917C14983D34, dev 1024, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
Filesystem LNZFS01_3bankenintras_1:
fs LNZFS01_..nintras_1 RepTg, EVS 1, cap 306, con 550 , perm 2BC85008120B35F2, dev 1026, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_CIFSDIV RepTg, EVS 1, cap 1278, con 1536 , perm 2BC8510398D17EE8, dev 1027, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_LNZWRKFLX01 RepTg, EVS 1, cap 2178, con 3072 , perm 2BC341A35ACABBA8, dev 1049, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_btvdaten_1 RepTg, EVS 1, cap 2232, con 2458 , perm 2BC80254C65F85CC, dev 1030, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_dbedaten_1 RepTg, EVS 1, cap 5112, con 6144 , perm 2BC8BBCDC4E25CAF, dev 1033, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_dbedaten_2 RepTg, EVS 1, cap 11952, con 12288 , perm 2BC34416A56011FE, dev 1050, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_dbvdaten_1 RepTg, EVS 1, cap 432, con 862 , perm 2BC86F120FCF0A1E, dev 1025, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_obkdaten_1 RepTg, EVS 1, cap 18720, con 20480 , perm 2BC841709C478675, dev 1029, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_obkdaten_2 RepTg, EVS 1, cap 10980, con 14336 , perm 2BC8F0625C01DBFF, dev 1032, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
fs LNZFS01_obkdaten_3 RepTg, EVS 1, cap 8532, con 9421 , perm 2BC344B47D8779B7, dev 1051, 4KiB, WFS-2, DSBs: 128, DWB: Yes , Thin: No, AX: ????
------------------------------
Albert Hagopian
Software Development Engineer - Specialist
Hitachi Vantara
------------------------------
Original Message:
Sent: 03-28-2024 04:44
From: Miran Kreuzer
Subject: Remove SDs from NAS Storage Pool
Hello,
how can i remove SDs from an NAS Storage Pool? What i have found so far, is to use the span-unmap-vacated-chunks command and then remove the Pool Volumes. But i couldn't find how to remove them in a correct way. Would it be correct to deny access to the SDs i want to remove and then forget the SDs and unmap them on the Storage Controller?
Regards
Miran
------------------------------
Miran Kreuzer
3 Banken IT GmbH
------------------------------