This is fixed in ESXi 6.7 U1, released 2018-10-16, and ESXi 6.5 P03, released 2018-11-29.
As a work around, the automatic unmap feature can be disabled:
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/6-5/vsphere-storage-6-5/storage-provisioning-and-space-reclamation-in-vsphere/storage-space-reclamation-in-vsphere/space-recalmation-on-vsphere-vmfs-datastores/configure-fixed-reclamation-for-the-existing-vmfs6-datastore.html