Peer Persistence nimble showing the volume used but there is no VM or snapshots remaining

[Haroonh]

Hi,

We have an DHCI environment with peer persistence volumes,  initially we put some data on the volumes and had snapshots. but after moving the VMs and deleting the snapshots Nimble still reports the volumes as used.

how can we find out what's taking that space and also how to remove anything which is on it to reuse them.

Kind Regards,

[Nick_Dyer · Accepted solution]

Hi,

When working with block storage blocks they're seen as 'written' or consumed when you write data to them. If you then delete/change/update the host-side dataset within the app/server, the block storage volume will still see those blocks as consumed on the array - it has no visiblity to what the application or host has done. In your case, you've deleted/vMotioned the VM, but the blocks are still 'touched' and thus showing as used on the array.

The answer here is to use things like SCSI UNMAP within VMware, which re-thins the volume from the host side to the array and removes the previously used blocks.

If you need any assistance at any time, please give Nimble Support a call who would be happy to walk through this with you.