How can volume usage be greater than volume size.
I have seen this before at one of my customers.
Please call support. I believe this is a bug that is fixed in the latest release (currently 3.3).
Please let us know what support said.
I had this issue as well.... ended up opening a case with Nimble. They wanted us to follow this VMware article. https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513
In the end this didn't help us and we had to storage vmo to a new datastore to reclaim the space.
Maybe Nimble is accounting for metadata? Also, it looks like the data is incompressible in which case trying to apply compression can slightly increase the data usage. I believe I've read (though I can't find it right now) that the LZ4 compression employed by NimbleOS has a worst case inflation of roughly 3% which is what you're seeing. If you do have compression enabled, would it be possible to copy your data to another volume that has it turned off to see if you get the same result?
Responce from support
The reason for volume reporting incorrect space usage is, high IO and generation deletions are falling behind and all the space locked up in those deletions generations are being reported in the volume usage.
This is a known issue and the fix for this is addressed in the release NOS 3.X which is still a release candidate and not recommended for production critical environments. However, Nimble support would notify you, upon NOS 3.X getting into general availability.
Thanks for letting us know Tim!
Retrieving data ...