This issue is resolved in vCloud Availability 3.5.1, available at Support Documents and Downloads (broadcom.com).
Workaround:
To work around this issue if you do not want to upgrade, delete the placeholder independent disk VMDK files that are referenced in the vCenter Server events. On the next independent disk size check, the VMDK files will be recreated.
Note: Active replications will not be impacted by following the steps below, only vCloud Director storage reporting will be impacted until the new VDMK files are recreated.
- In the vSphere Client go to Monitor > Events for the affected vCenter Server.
- Identify the unique C4 VMDK files reported in the events.
Example:
"Cannot complete the operation because the file or folder [DATASTORE] C4-b82b42bb-####-####-####-########ac2 (2f83fada-####-####-####-########b26)/C4-b82b42bb-####-####-####-########ac2
(2f83fada-####-####-####-########b26)_changed.vmdk already exists"
- SSH to an ESXi host that has access to the datastore the C4 VM resides on and log in as root.
- Navigate to the C4 VM directory obtained from the event message.
Example:
cd /vmfs/volumes/DATASTORE/"C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)"
- List the contents of the directory.
Example:
-rw-r--r-- 1 root root 0 Oct 9 21:36 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26).vmsd
-rw-r--r-- 1 root root 303 Oct 9 21:36 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26)-2bc9383d.hlog
-rw------- 1 root root 1.6G Nov 29 22:23 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26)-flat.vmdk
-rwxr-xr-x 1 root root 2.1K Nov 29 22:23 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26).vmx
-rw------- 1 root root 546 Nov 29 22:23 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26).vmdk
-rw------- 1 root root 1.6G Nov 29 23:03 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26)_changed-flat.vmdk
-rw------- 1 root root 554 Nov 29 23:04 C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26)_changed.vmdk
- Remove both the -flat.vmk and .vmdk files for the disk referenced in the event message.
Example:
rm C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26))_changed.vmdk
rm C4-b82b42bb-####-####-####-########ac2(2f83fada-####-####-####-########b26))_changed-flat.vmdk
- Repeat steps 4-6 for all other VMDK files referenced in vCenter events.