Unsolved
1 Rookie
•
79 Posts
0
1863
September 28th, 2021 11:00
How do you reclaim storage from written devs
What are the steps required to reclaim storage back to the pool on a VMAX 40K running Enginuity 5876.286.194?
I can remove and unmap the dev, dissolve and delete, but I don't see any changes to the pool free column. Am I suppose to just remove the dev from the Storage Group(s) and drain the dev? I looked into the symconfigure using the "free tdev" or "start reclaim", but it seems those options just reclaims unwritten storage rather than reclaiming the whole dev back to the pool. Any help would greatly be appreciated.
Thanks
No Events found!
DELL-Sam L
Moderator
•
7.6K Posts
0
September 29th, 2021 09:00
Hello macyero,
.Here is a link to a KB that maybe of assistance. https://dell.to/3ierQaI
macyero
1 Rookie
•
79 Posts
0
September 29th, 2021 17:00
Thank you Sam
So based on the the knowledge base I would do the following:
Instead of unmapping I would just set the dev to not_ready
# symaccess -sid xxxx -type storage -name MY_SG remove dev 1ABC
# symdev -sid xxxx not_ready 1ABC
# symdev -sid xxxx free -all on tdev 1ABC
# symdev -sid xxxx ready 1ABC
# symcfg discover
# symcfg -sid xxxx list -thin -pool -GB -detail
Do I need to include the range?
DELL-Sam L
Moderator
•
7.6K Posts
0
September 30th, 2021 13:00
Hello macyero,
You don’t need to include a range.
macyero
1 Rookie
•
79 Posts
0
September 30th, 2021 15:00
The command I posted earlier was incorrect. It should be the following:
symdev -sid xxxx free -all 1ABC
although when I tried it I get the following message:
"The requested feature is not supported for this microcode or SYMAPI version"
Any suggestions on how to get around this?
Thanks
macyero
1 Rookie
•
79 Posts
0
October 1st, 2021 09:00
Hi Sam,
I tried the command. Seems its not supported because of the microcode or the SYMAPI version. Here is the example I ran as follows:
[rootj ~]# symdev -sid xxx free -all 1ABC
Execute a 'FreeAll Start' Device operation for device '1ABC' (y/[n]) ? y
The requested feature is not supported for this microcode or SYMAPI version
Would it be better to delete the dev, create a new one and bind it to the pool? If so, what best practices do you recommend? I need to reclaim a lot of LUNs so if there is a way to do that, that would be great.
Thanks
DELL-Sam L
Moderator
•
7.6K Posts
0
October 1st, 2021 09:00
Hello macyero,
That is the correct command. It will ask you if you want to set the range and you can select yes or no. once you chose yes or no then it will start the process.
macyero
1 Rookie
•
79 Posts
0
October 1st, 2021 10:00
Thank you Sam
I would open a case with Dell, but the array is no longer under Support. If there are steps to create a new tdev and add those to the pool that would be fine. I just need to expand the pool. Its just when I delete the device it doesn't reclaim the storage back to the pool like how its done on the mid-range arrays. Since I cannot run free -all command I would like to expand the thin pool by adding more devs if thats possible? Does it require creating hypers?
Thanks,
DELL-Sam L
Moderator
•
7.6K Posts
0
October 1st, 2021 10:00
Hello macyero,
You are going to need to open a support case for this issue.
https://dell.to/3okmE9c
macyero
1 Rookie
•
79 Posts
0
October 1st, 2021 16:00
What if I ran "symdev -sid xxxx list -noport" to get all of the available TDVs that are not bound to a pool and add the selected TDEVs to the thin pool:
symconfigure -sid xxxx -cmd "add dev AAAA:BBBB to pool T_Pool_1, type=thin, member_state=ENABLE;" commit -v -nop
If there are TDEVs from the list -noport command that had written data wouldn't the thin pool show only what free? I assume once the TDEVs get added to a Storage Group the host would need to format the volume to zero out? Is there any way to zero out or format TDEVs on the array?
Thanks,