Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VM disk errors for vCloud Availability placeholder independent disks repeat in the events view of the vSphere Client (76595)

Last Updated: 3/12/2020Categories: TroubleshootingTotal Views: 3305Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

In the Events view of the vSphere Client, you see entries similar to:

"Cannot complete the operation because the file or folder [XX-AAD2-BB20-F-01] C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)/C4-b82b42bb-5912-40e3-b595-eb5351877ac2
(2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmdk already exists"

(2f83fada-1c7a-4110-9b30-ac88a08c2b26)_changed.vmdk already exists"

In the vCloud Availability Portal, all replications are in a healthy state.

In /var/log/vmware/vpxd/vpxd.log on the vCenter Server appliance, you see entries similar to:

2019-12-17T17:09:15.551Z info vpxd[7F0CDECD9700] [Originator@6876 sub=vpxLro opID=34d9b0b5-76e3-4b37-a420-595d03b3f5ee_ND_GI-cd] [VpxLRO] -- BEGIN task-333656 -- virtualDiskManager -- vim.VirtualDiskManager.createVirtualDisk -- 527c5a88-b743-1c60-182b-109914c2a612(521c9e62-2d6c-0a26-8a76-f59d8a0c4e53)
2019-12-17T17:09:15.585Z info vpxd[7F0D05A75700] [Originator@6876 sub=vpxLro opID=34d9b0b5-76e3-4b37-a420-595d03b3f5ee_ND_GI-cd] [VpxLRO] -- FINISH task-333656
2019-12-17T17:09:15.585Z info vpxd[7F0D05A75700] [Originator@6876 sub=Default opID=34d9b0b5-76e3-4b37-a420-595d03b3f5ee_ND_GI-cd] [VpxLRO] -- ERROR task-333656 -- virtualDiskManager -- vim.VirtualDiskManager.createVirtualDisk: vim.fault.FileAlreadyExists:
--> Result:
--> (vim.fault.FileAlreadyExists) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    file = "[XX-AAD2-BB20-F-01] C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)/C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmdk"
-->    msg = "Cannot complete the operation because the file or folder [XX-AAD2-BB20-F-01] C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)/C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmdk already exists"
--> }
--> Args:
-->
--> Arg name:
--> "[XX-AAD2-BB20-F-01] C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)/C4-b82b42bb-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmdk"
--> Arg datacenter:
--> 'vim.Datacenter:datacenter-21'
--> Arg spec:
--> (vim.VirtualDiskManager.FileBackedVirtualDiskSpec) {
-->    diskType = "thin",
-->    adapterType = "lsiLogic",
-->    capacityKb = 41918464,
-->    profile = <unset>,
-->    crypto = (vim.encryption.CryptoSpec) null

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue can occur due to various environmental issues external to vCloud Availability at the time the placeholder independent disk size is being modified.

Common environmental issues that can cause this are:

vCenter Server performance resulting in slow response times.

Network issues impacting component communication.

Resolution

This issue is resolved in vCloud Availability 3.5.1, available at VMware Downloads.

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-5912-40e3-b595-eb5351877ac2 (2f83fada-1c7a-4110-9b30-ac88a08c2b26)/C4-b82b42bb-5912-40e3-b595-eb5351877ac2
(2f83fada-1c7a-4110-9b30-ac88a08c2b26)_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-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmsd
-rw-r--r--    1 root     root         303 Oct  9 21:36 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26)-2bc9383d.hlog
-rw-------    1 root     root      1.6G Nov 29 22:23 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26)-flat.vmdk
-rwxr-xr-x    1 root     root        2.1K Nov 29 22:23 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmx
-rw-------    1 root     root         546 Nov 29 22:23 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26).vmdk
-rw-------    1 root     root      1.6G Nov 29 23:03 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26)_changed-flat.vmdk
-rw-------    1 root     root         554 Nov 29 23:04 C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26)_changed.vmdk

Remove both the -flat.vmk and .vmdk files for the disk referenced in the event message.

Example:
rm C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26))_changed.vmdk
rm C4-b82b42bb-5912-40e3-b595-eb5351877ac2(2f83fada-1c7a-4110-9b30-ac88a08c2b26))_changed-flat.vmdk

Repeat steps 4-6 for all other VMDK files referenced in vCenter events.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
vCloud Director Appliance のインストールのベスト プラクティス (76559)

KB
•
vCloud Director 设备安装最佳实践 (76559)

KB
•
只有在具有可关联实体类型的类别时，才能从 UI 创建计算策略 (76576)

KB
•
为不同于 vRealize Automation 虚拟设备的域配置 Kerberos (76634)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability 3.5.x

Take Our Survey

Support Assistant