This is an expected behavior, where the format of a virtual disk in multiwriter mode is changed to an unsupported format. For more information about the requirements of virtual disks in multiwriter mode, see Enabling or disabling simultaneous write protection provided by VMFS using the multi-writer flag (1034165).
To confirm the issue, verify the virtual disk format. To check the disk format, see Determining if a VMDK is zeroedthick or eagerzeroedthick (1011170).
To prevent this issue from re-occurring, ensure that virtual disks in multiwriter configurations are not converted to the lazyzeroedthick format. To use disks in multiwriter mode, the format must be Thick Provision Eager Zeroed.
To work around this issue if you need to extend a virtual disk in a multiwriter configuration, extend the virtual disk by running the vmkfstools -X command from the ESXi/ESX host command line (this is vSphere Client default behavior). This ensures that the virtual disk format stays in the correct eagerzeroedthick format.
For example, to extend the size of the virtual disk to 60 GB:
# vmkfstools -X 60G -d eagerzeroedthick /vmfs/volumes/Datastore_name/virtual_Machine_folder/virtualmachinedisk.vmdk
Notes: