Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
HPE StoreVirtual Storage / LeftHand
cancel
Showing results for 
Search instead for 
Did you mean: 

P4500 storage array volume utilization is more that allocated size

viv_nan
Occasional Advisor

P4500 storage array volume utilization is more that allocated size

HI all,

P4500 I have allocated 8x500gb volume to 6 x VMware ESX host shared with Thin provisioning enabled network RAID 1+0 (2way), when I see the used summary and volume use tab it shows me different value( more that what allocated)

first volume utilied 520 gb , second 300, third 200gb , rest are not utilized

Is this this a normal opertaion or ?
3 REPLIES
Steven Clementi
Honored Contributor

Re: P4500 storage array volume utilization is more that allocated size

Ok, so....

You are using RAID 1+0 (2-way)...

So effectively... you are doubling up on the available storage? 500GB allocated would be 1TB out of the total?

What is your "Provisioned" space value(s)?


Steven
Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)
viv_nan
Occasional Advisor

Re: P4500 storage array volume utilization is more that allocated size

Please find the attached screenshot

is that a normal operation
teledata
Respected Contributor

Re: P4500 storage array volume utilization is more that allocated size

That looks correct. RAID 1 + 0 can consume up to 200% of the volume size. Plus if you create snapshots it can be up to 200% plus 2x the size of all your snapshot deltas.

There are a few things to keep in mind with thin provisioning as well:

1) To get the highest utilization also thin provision your VMFS volumes

2) Be sure to only do "quick" formats within Windows, a "full" will "touch" every block therefore fully provision.

3) don't defrag volumes, this also will negate thin provisioning.

http://www.tdonline.com