Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When running virtual machines with Changed Block Tracking (CBT) enabled, on an ESXi 5.0 patch 10 or later host. After a virtual machine failover, you experience these symptoms: Attempting to power on the virtual machine from the vSphere Client returns the error:Could not open/create change tracking file Changed Block Tracking (CBT) is enabled on the virtual machine, as detailed in Enabling Changed Block Tracking (CBT) on virtual machines (1031873) The virtual machine is running on ESXi 5.0, Patch 10 or later The virtual machine is failed over by High Availability (HA) or VMware Site Recovery Manager (SRM). When browsing the virtual machine's home directory, you see a directory named: <VM name>-ctk.vmdk.lck. In the vmware.log file of the virtual machine, you see entries similar to: <YYYY-MM-DD>T<time>.943Z| vmx| FILE: WaitForPossession timeout on '/vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM-ctk.vmdk.lck/M04881.lck' due to another machine (uuid=31-32-34-36-36-30-55-41-44-33-31-30-30-30-58-36)<YYYY-MM-DD>T<time>.946Z| vmx| FILE: FileIO_Lock on '/vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM-ctk.vmdk' failed: Lock timed out<YYYY-MM-DD>T<time>.946Z| vmx| DISKLIB-CTK : Could not open tracking file. File open returned IO error 4.<YYYY-MM-DD>T<time>.946Z| vmx| DISKLIB-CTK : Could not open change tracking file "/vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM-ctk.vmdk": Could not open/create change tracking file.<YYYY-MM-DD>T<time>.946Z| vmx| DISKLIB-LIB : Could not open change tracker /vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM-ctk.vmdk: Could not open/create change tracking file.<YYYY-MM-DD>T<time>.946Z| vmx| DISKLIB-VMFS : "/vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM-flat.vmdk" : closed.<YYYY-MM-DD>T<time>.946Z| vmx| DISKLIB-LIB : Failed to open '/vmfs/volumes/54ff811d-5920eb88-7848-2c768a545464/Datastore/VM.vmdk' with flags 0xa Could not open/create change tracking file (2108).</time></time></time></time></time></time></time>Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This issue occurs due to change tracking lock files which remain locked by the ESXi host that the virtual machine was running on before the failover occurred.
Exercise caution when deleting files in the virtual machine home directory. Delete only the named lock file directory.
This is a known issue affecting virtual machines running on ESXi 5.0, patch 10 and later. This issue is resolved in VMware ESXi 5.0, Patch Release ESXi500-201510401, release name ESXi500-201510401, available at VMware Product Patches. For more information, see VMware ESXi 5.0, Patch Release ESXi500-201510001 (2113684). Note: This issue only affects ESXi 5.0 hosts, running patch 10 and later. ESXi 5.1 is not affected. To work around this issue, delete the lock files that are preventing the virtual machine from powering on. To delete the lock files: Open the vSphere Client. Navigate to the virtual machine home directory using the datastore browser. Delete the lock files folder and all contents. The directory is named: *-ctk.vmdk.lck Power on the virtual machine.
For information about mapping ESXi patch numbers to build numbers, see Correlating VMware products build numbers to update levels (1014508).Correlating build numbers and versions of VMware productsEnabling or disabling Changed Block Tracking (CBT) on virtual machinesVMware ESXi 5.0, Patch Release ESXi500-201510001VMware ESXi 5.0, Patch ESXi500-201510401-BG: Updates esx-base仮想マシンのパワーオンが次のエラーで失敗する: 変更追跡ファイルのオープン/変更ができませんでした打开虚拟机电源失败，并出现以下错误：无法打开/创建更改跟踪文件 (Could not open/create change tracking file)