vSAN ESA File services is not reclaiming space on a file share.

Products

• VMware vSAN

Issue/Introduction

Symptoms:

Shared folder(s) on the vSAN ESA File Server appliance continuously grow in size.

Deleting files from the share does not reduce the reported used space.

Performance degradation due to storage pressure may be observed.

 

Environment

VMware vSAN 8.x

Cause

• Deleting files in a file share might not be reflected in vSAN capacity view.

For more information find the documents for Deleting files in a file share might not be reflected in vSAN capacity view.

• The allocated blocks may not be returned back to the vSAN storage instantly after all the files are deleted and hence it would take some time before the reclaimed storage capacity to be updated in vSAN capacity view. Also, when new data is written to the same file share, these deleted blocks might get reused prior to returning them to vSAN storage.
• If unmap is enabled and vSAN deduplication is disabled, the space may not be freed back to vSAN unless 4MB aligned space are freed in VDFS. If unmap is enabled and vSAN deduplication is enabled, space freed by VDFS will be freed back to vSAN with a delay.

Resolution

Workaround:

In cases where space reclamation is an urgent priority, then delete the share, recreate it and restore contents from backup. 

NOTE: Make sure all the data is backed up prior this operation.