HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Application Integration
Showing results for 
Search instead for 
Did you mean: 

Free Space in vSphere vs. What Nimble Reports

Go to solution
Occasional Visitor

Free Space in vSphere vs. What Nimble Reports

Brand new to Nimble....so forgive my ignorance

I've created a 500GB volume and migrated 3 servers into that volume.  vCenter sees that volume with 509GB provisioned and 22GB free space left.

Nimble reports that the volume is using 237GB, so I should have over 250GB of free space on that volume.  However, since vCenter doesn't see what Nimble sees I cant move any more servers onto that volume.  vSphere reports "Insufficient disk space on datastore xxx".

Is this by design?  Or am I missing something?

Honored Contributor

Re: Free Space in vSphere vs. What Nimble Reports

Hey Bryan

Welcome to Nimble and Nimble: Connect !!

VMWare ESX will write to it's datastore as if it's a regular disk... the Nimble array will compress that data in-line (with no degradation to performance) so although ESX is reporting it's stored 500GB, the array has compressed that into the 237GB  (saving you the space in return)

If you've not done so already register the Nimble vCenter Management plugin as this will allow your vCenter server to view the Nimble volumes (plus much more)

Feel free to post back if you need more info or have more questions



Valued Contributor

Re: Free Space in vSphere vs. What Nimble Reports

Look in the downloads section under KB Articles for "


KB-000079 Oct 9, 2013


Compression and VMFS Free Space Reported


Valued Contributor

Re: Free Space in vSphere vs. What Nimble Reports

Hi Bryan,

               This had me baffled for a moment until I realised exactly what the KB article outlined. Probably a reason for some SAN admins preferring not to use thin provisioning. The simplicity of reporting available usage and space on the Nimble GUI makes me for one comfortable with thin provisioning and compression. The other thing that threw me was the SCSI UNMAP.  Have a quick read about this and you will have a little more clarity about what one system says versus your Nimble array.