Page 1 of 1
How to reclaim space after removing virtual volume 3PAR?
Posted: Mon Feb 10, 2014 5:37 am
by darionsr
Hello, (thanks for letting me belongs to this community)
I have an Inserv F200 3PAR. I've deleted 2 virtual volumes of 3PAR. Before the deletion it had 410GB free and now continues to have 410GB. How I can refresh this information? I read about reclaim space in 3PAR, but do not find the way to do.
Thanks for your help.
Regards.
Re: How to reclaim space after removing virtual volume 3PAR?
Posted: Mon Feb 10, 2014 11:46 am
by Richard Siemers
Compact the CPG where the VVs were deleted.
Keep in mind there are various levels of free space.
Unallocated free space, ready to be used by any CPG.
Free space inside the CPGs and Logical Disks
Free space inside the VVs
Re: How to reclaim space after removing virtual volume 3PAR?
Posted: Tue Feb 11, 2014 9:44 am
by darionsr
Thanks Richard Siemers,
I'll try your solution. I had tried to compact the CPG from Inform, but "compact CPG..." option was disabled.
I'll remember your advices.
Re: How to reclaim space after removing virtual volume 3PAR?
Posted: Thu Nov 27, 2014 2:21 pm
by trarun0483
Hi you can very well run the compact cpg from CLI option. Below is dry run mode to see how much space you will gain for respective CPG
HP3Par1 cli% compactcpg -dr SQL_FC_SS6
Compacting CPG SQL_FC_SS6
Initial trim would reclaim 0 MB SA space, 0 MB SD space, and 0 MB USR space.
Would move 0 MB SA space, 0 MB SD space, and 0 MB USR space.
Final trim would reclaim 0 MB SA space, 0 MB SD space, and 0 MB USR space.
Re: How to reclaim space after removing virtual volume 3PAR?
Posted: Fri Nov 28, 2014 8:51 am
by JohnMH
It depends on where you're looking for the space to be returned to.
When you delete volumes the chunklets first need to be cleaned before they are returned for use by the system, this is especially true for fpvv's as every chunklet is allocated upfront and so must be cleaned (zero's out) on deletion, you can see this by running the below.
CLI% showsys -space
If the uninitialized value is >0 it’s likely a large amount of data has been deleted and the blocks are in the process of being zero’d out before being returned to the system free pool. This process takes time and for non thin volumes every block allocated regardless of whether it was written needs to be zero’s out. There's no way to increase the speed of this process but it's only usually encountered during testing when large fully provisioned volumes are created, torn down and then recreated.
To view the cleaning process you can use :
CLI% showpdch –cng Specifies that information for chunklets that are being cleaned (reclaimed and zero’d after deletion) by the system are displayed, you can also use CLI% showpd –c
Once they're all clean a compactcpg which you should schedule will return these to the pool.