vvol testing – provisioned space almost double total capacity, without any VMs in it

This post was originally published on this site

Hello, we’re testing out vvols in 6.7 with the idea of eventually replacing our RDM-based windows failover cluster with vvol-based WFCS. My first time dealing with vvols, and I’ve had about a year of experience working with vsphere making and using vms. Not much with the storage aspect of vmware.

 

We use a Dell Compellant sc4020 array. As a test, I made a small, 20GB vvol storage container on the array. So far so good. I made a 5GB thin-prov volume on that array, assigned it to a test vm, once again, no problem.

 

Then I deleted that 5GB volume. Created a new 10GB one. Shared that 10GB volume with two future file server VMs. Have not brought the shared disk ‘online’ in windows yet. So the volume in vmware shows the “testFileServertestfileserver.vmdk” file within the storage container volume as being 0KB.

 

Yet, under the storage container’s capacity properties, total capacity reads “20 GB” as it should, but “provisioned space” reads “34 GB” and “free space” reads “6 GB”

 

where are these numbers coming from? Why would an essentially brand-new storage container that only has had 2 volumes put into it, one of them deleted, be saying that my provisioned space is already up to 34GB?

 

I did notice that the 10GB volume’s settings say that it can have a “maximum size” of 16GB, which would at least explain some of where the space has gone.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.