An administrator attempts to manually reclaim space on thin-provisioned VMFS6 volumes but finds that no
additional space is being recovered.
Which could be causing this?
A.
vSphere 6.5 does not support manual UNMAP.
B.
The manual UNMAP operation has been moved to the vSphere web client.
C.
The VASA version is use is incompatible.
D.
UNMAP is automated for VMFS6.
Explanation:
VMFS 6 is the new filesystem of vSphere 6.5. The new filesystem supports 512e advanced format drives and is
4098 sector (4K) aligned. It also supports automatic UNMAP, which asynchronously tracks freed blocks and
sends UNMAPs to backend storage in background.
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2147824
D
5
0
On VMFS6 datastores, ESXi supports the automatic asynchronous reclamation of free space. VMFS6 can run the unmap command to release free storage space in the background on thin-provisioned storage arrays that support unmap operations.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-BC1A172C-E649-4812-B8B2-A9E45AC97051.html
1
0
When you create a VMFS6 datastore, you can modify the default parameters for automatic space reclamation. You can also change granularity and priority or disable space reclamation for your VMFS6 datastore.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-98901BEE-8675-4D39-8AA2-E790EE341986.html
0
0