web vsphere client 6.5 setup wm with vmdk file

If you run it while performing other datastore management operation, such as creating or extending a datastore, you might experience delays and other problems. Storage rescan is an IO intensive operation. Using storage rescan in environments with the large number of LUNs might cause unpredictable problems.You can see the Unmap not supported message in the vmkernel.log file.Workaround: None. If the unmap granularity of the backing storage is greater than 1 MB, the unmap requests from the ESXi host are not processed. ESXi does not support the automatic space reclamation on arrays with unmap granularity greater than 1 MB.If the datastore is created on a 512e device, expand the datastore with 512e devices.Workaround: None. If the VMFS6 datastore is backed by a 512n device, expand the datastore with the 512n devices. You can expand a VMFS6 datastore only with the devices of the same type. VMFS6 datastore does not support combining 512n and 512e devices in the same datastore.Perform the rescan-vmfs operation on all host connected to the volume.Run the vmkfstools -growfs command on one of the hosts connected to the volume.As a result, you might observe inconsistent information in VIM APIs and LVM commands on the host.Workaround: Perform these steps:

This problem occurs when you attempt to grow the datastore while the backing SCSI device enters the APD or PDL state. After failed attempts to grow a VMFS datastore, VIM APIs information and LVM information on the system is inconsistent.This might be useful to all the guys who deal with storage related issues day in an out: VMFS Issues

Web vsphere client 6.5 setup wm with vmdk file