Actual Disk space vs VMFS space (tpvv and EZT)
Posted: Tue Oct 23, 2012 2:54 pm
We are new to 3PAR and just putting our first vm's on. I created four 4TB virtual volumes in the IMC as thin with zero detect. I presented those to my ESXi 5.1 hosts and created a datastore cluster out of them so that I could use sDRS in VMWare. I am now migrating existing vm's from an EVA8400 to the 3PAR volumes with svMotion. When I do my svMotion I am changing destination format to Lazy Zeroed to Eager Zeroed Thick (EZT).
All has been going well but now I have a problem/question. My virtual volume on the 3PAR is working great - says that of the 4TB only 2TB is used, however, VMWare is calculating the VMFS space based on an EZT vmdk and is calculating the thick size. SO....what is being stored as 2TB on my 3PAR is showing up as 3.4TB in vSphere so it thinks the volume is almost out of space. I am not sure how to reconcile this. I suppose I could do thin on thin and then the VMFS would match what is happening on the 3PAR (?) but I have heard this isn't necessarily the best way to go.
Any suggestions?
All has been going well but now I have a problem/question. My virtual volume on the 3PAR is working great - says that of the 4TB only 2TB is used, however, VMWare is calculating the VMFS space based on an EZT vmdk and is calculating the thick size. SO....what is being stored as 2TB on my 3PAR is showing up as 3.4TB in vSphere so it thinks the volume is almost out of space. I am not sure how to reconcile this. I suppose I could do thin on thin and then the VMFS would match what is happening on the 3PAR (?) but I have heard this isn't necessarily the best way to go.
Any suggestions?