Richard Siemers wrote:Also ESX 6.5 and VMFS6 support the automatic unmap of deleted data. ESX 6.5 and VMFS5 do not. Remember to check your datastore VMFS versions.
Just be aware that last time I checked, this required the VMDK to be "thin".
3PAR VV for datastores Vmware
Re: 3PAR VV for datastores Vmware
Just be aware that last time I checked, this required the VMDK to be "thin".
The views and opinions expressed are my own and do not necessarily reflect those of my current or previous employers.
-
Richard Siemers
- Site Admin
- Posts: 1333
- Joined: Tue Aug 18, 2009 10:35 pm
- Location: Dallas, Texas
Re: 3PAR VV for datastores Vmware
MammaGutt wrote:Just be aware that last time I checked, this required the VMDK to be "thin".
That is 100% correct for in-guest unmap on a VMFS datastore, to pass trim/unmap commands from a guest-os/filesystem to VMFS6, and then onto the LUN. I just read that VMware is also converting guest ata TRIM commands into scsi UNMAP commands.
Vmware VVOLs, and RDMs in-guest unmap talks directly to the LUN. Note: linux unmap support needs virtual hardware version 11 or higher.
Deleting or moving VMDKs will auto unmap using VMFS6 regardless if the vmdk was thick or thin.
Richard Siemers
The views and opinions expressed are my own and do not necessarily reflect those of my employer.
The views and opinions expressed are my own and do not necessarily reflect those of my employer.