This post is more than 5 years old
76 Posts
1
960
July 9th, 2012 15:00
Reclaim space from offline/decommissoned server
Okay, now I need to reclaim the storage from an offline/decommissoned server. I know the space is still reserved somewhere out there, even though the Symmetrix database says there's no devices attached to that server anymore.
First, the evidence:
[# symmask list logins |
Symmetrix ID | : xxxxxxxxxxxx28 |
Director Identification : FA-8D
Director Port | : 0 |
User-generated | Logged On | |||
Identifier | Type Node Name | Port Name | FCID In | Fabric |
---------------- ----- --------------------------------- ------ ------ ------
50060b0000111120 Fibre tan | td2 | b20100 Yes | Yes |
Director Identification : FA-9D Director Port : 0 User-generated Logged On Identifier Type Node Name Port Name FCID In Fabric ---------------- ----- --------------------------------- ------ ------ ------ 50060b0000c99a86 Fibre tan fcd0 4a0400 Yes Yes |
I believe device 0060 was masked and attached to this server. Why? Because I can't find 0060 attached to anything else on FA 8D:0 & 9D:0:
# symmaskdb list assignment -dev 0060
No device masking database records could be found for the specified input parameters
# symdev list -v -dev 0060 | more |
Symmetrix ID: xxxxxxxxxx28
Device Physical Name | : Not Visible |
Device Symmetrix Name | : 0060 | |
Device Serial ID | : N/A | |
Symmetrix ID | : xxxxxxxxx28 |
Attached BCV Device | : N/A |
Attached VDEV TGT Device : N/A |
Vendor ID | : EMC | ||
Product ID | : SYMMETRIX | ||
Product Revision | : 5773 | ||
Device WWN | : 60060480000190105528533030303630 | ||
Device Emulation Type | : FBA | ||
Device Defined Label Type: N/A | |||
Device Defined Label | : N/A | ||
Device Sub System Id | : 0x0001 | ||
Cache Partition Name | : DEFAULT_PARTITION |
Device Block Size | : 512 |
Device Capacity | |||
{ | |||
Cylinders | : | 38105 | |
Tracks | : | 571575 | |
512-byte Blocks | : 73161600 | ||
MegaBytes | : | 35723 | |
KiloBytes | : 36580800 |
Geometry Limited | : No | |
} |
Device External Identity | ||
{ | ||
Device WWN | : 60060480000190105528533030303630 |
Front Director Paths (2): | ||
{ | ||
----------------------------------- | ||
DIRECTOR PORT | LUN | |
---------- ---- -------- --------- | ||
Type Num | Sts VBUS TID SYMM Host | |
----------------------------------- | ||
FA 08D:1 RW 000 00 07D N/A <============ | ||
FA 09D:1 RW 000 00 07D N/A <============ | ||
} |
Meta Configuration | : Striped | |||||
Meta Stripe Size | : 960k | (1 Cylinders) | ||||
Meta Device Members (17) : | ||||||
{ | ||||||
---------------------------------------------------------------------- | ||||||
BCV DATA | RDF DATA | |||||
---------------------------- -------------------------- | ||||||
Sym | Cap | Std Inv BCV Inv Pair | R1 Inv R2 Inv Pair | |||
Dev | (MB) Tracks Tracks State | Tracks Tracks State | ||||
---------------------------------------------------------------------- | ||||||
005F 35723 | - | - N/A | - | - N/A | ||
--> 0060 35723 | - | - N/A | - | - N/A | ||
0061 35723 | - | - N/A | - | - N/A | ||
0062 35723 | - | - N/A | - | - N/A | ||
0063 35723 | - | - N/A | - | - N/A | ||
0064 35723 | - | - N/A | - | - N/A | ||
0065 35723 | - | - N/A | - | - N/A | ||
0066 35723 | - | - N/A | - | - N/A | ||
0067 35723 | - | - N/A | - | - N/A | ||
0068 35723 | - | - N/A | - | - N/A | ||
0069 35723 | - | - N/A | - | - N/A | ||
006A 35723 | - | - N/A | - | - N/A | ||
006B 35723 | - | - N/A | - | - N/A | ||
006C 35723 | - | - N/A | - | - N/A | ||
021D 35723 | - | - N/A | - | - N/A | ||
021E 35723 | - | - N/A | - | - N/A | ||
021F 35723 | - | - N/A | - | - N/A | ||
---------------------------------------------------------------------- | ||||||
607298 | - | - | - | - | ||
} |
# symdev list -dev 0060
Symmetrix ID: xxxxxxxxxxxx28
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
0060 Not Visible ***:* 01A:D1 RAID-6 N/Grp'd (m) RW -
# symmaskdb list capacity -host tan
Symmetrix ID : xxxxxxxxxx28
Host Name : tan
Identifiers Found : 50060b0000111120
50060b0000c99a86
Device Cap(MB) Attr Dir:P
------ ------- ---- ----
-----------------------------
MB Total: 0
GB Total: 0.0
And lastly.. device 0060 doesn't show up in the "noport" list.. so it's assigned to something.
# symdev list -noport | more
Symmetrix ID: xxxxxxxxx28
Device Name Directors Device
--------------------------- ------------- -------------------------------------
Cap
Sym Physical SA DA :IT Config Attribute Sts (MB)
--------------------------- ------------- -------------------------------------
0055 Not Visible ???:? 01D:DA 2-Way Mir N/Grp'd RW 3
0056 Not Visible ???:? 16A:CB 2-Way Mir N/Grp'd RW 3
01FE Not Visible ???:? 01A:C0 RAID-6 N/Grp'd RW 61425
01FF Not Visible ???:? 01D:D2 RAID-6 N/Grp'd RW 61425
020F Not Visible ???:? NA:NA VDEV N/Asst'd NR 35723
...
Device 0060 is just one example. Is there anyway to reclaim this device so that I can "unmeta" it and return the devices back to the pool? And is there anyway to identify other devices that were attached to the server which went offline and got decommissoned before I could return the space back to the pool?
Thanks.
dynamox
9 Legend
•
20.4K Posts
0
July 9th, 2012 19:00
so once device is unmasked you need to make it write disabled, unmap it and then dissolve it (if it's a meta). If you want to list all devices that are mapped but not masked:
symmaskdb -sid 123 list no_assignment
dynamox
9 Legend
•
20.4K Posts
0
July 9th, 2012 15:00
do you have that server's WWN ?
markdf
76 Posts
0
July 9th, 2012 15:00
# symmaskdb list capacity -host tan
Symmetrix ID : xxxxxxxxxx28
Host Name : tan
Identifiers Found : 50060b0000111120 <======
50060b0000c99a86 <======
but when I do a list assignment by WWN, says nothing is there:
# symmaskdb list devs -wwn 50060b0000c99a86
Symmetrix ID : xxxxxxxxxxx28
Originator Port wwn : 50060b0000c99a86
User-generated Name : tan/fcd0
No Devices were found for that WWN
markdf
76 Posts
0
July 10th, 2012 06:00
Dude.. I'm an idiot. Device 0060 is a meta member of 005F, which even says so in my output above.
Basically using the "no_assignment" command:
Director Identification : FA-8D
Director Port : 0
Devices not yet assigned :
020
2D1
2D5
2D9
318
31C
320
324
328
32C
Director Identification : FA-9D
Director Port : 0
Devices not yet assigned :
020
2D1
2D5
2D9
318
31C
320
324
328
32C
I just need to reclaim those devices (with the exception of 020 which seems attached to every FA, and says it's a VCM device, which I assume is the gatekeeper).
Thanks again. Sorry to bother ya on this one.
dynamox
9 Legend
•
20.4K Posts
0
July 10th, 2012 07:00
you are not bothering at all, you are learning ..that's why we all come here to do