6.0 linked clone errors with "File system specific implementation of LookupAndOpen [file] failed" in vmware.log file
Article ID: 313034
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- Virtual machine (VM) fails to start
- VM files fail to delete on datastore
- Virtual desktop infrastructure (VDI) Machine BSOD
- In the vmkernel.log, you see entries similar to:
2017-01-30T08:13:18.238Z cpu11:1319986)FSS: 5760: Conflict between buffered and unbuffered open (file 'ctf1461-checkpoint-sesparse.vmdk'):flags 0x4008, requested flags 0x1
- In the vmware.log, you see similar to:
2017-02-15T06:03:49.168Z| vmx| I125+ Power on failure messages: File system specific implementation of LookupAndOpen[file] failed
2017-02-15T06:03:49.168Z| vmx| I125+ File system specific implementation of OpenFile[file] failed
2017-02-15T06:03:49.168Z| vmx| I125+ File system specific implementation of LookupAndOpen[file] failed
2017-02-15T06:03:49.168Z| vmx| I125+ Failed to lock the file
2017-02-15T06:03:49.168Z| vmx| I125+ Cannot open the disk '/vmfs/volumes/5677c9eb-2b7c3b68-a4c2-645106ee4220/lwepc5438/lwepc5438-checkpoint.vmdk' or one of the snapshot disks it depends on.
2017-02-15T06:03:49.168Z| vmx| I125+ Module 'Disk' power on failed.
Environment
VMware vSphere ESXi 6.0
Cause
Data corruption during reclaim disk space of linked clone with sesparse vmdk.
Resolution
- If the problem is happening for cloned VMs, see Failed to power on cloned VM. Error: File system specific implementation of LookupAndOpen[file] failed
- There is a problem related to s sesparse file corruption bug for VDI VMs in ESXi 6.0. This has been resolved for ESXi 6.0 U3a. Fore more information see release notes and you can download the ESXi image here.
- For more information on the sesparse corruption bug affecting some versions of the ESXi OS, see Virtual Machines running on an SEsparse snapshot may report guest data inconsistencies
Workaround:
To workaround this issue for VDI VMs in ESXi 6.0, use any of the below workarounds
Workaround 1
Check and attempt to repair the disk.
- SSH to the ESXi host where the VM resides
- Check the file location:
vmkfstools -x check /vmfs/volumes/<datastorepath>/<vm name>/<vm name main base disk>.vmdk
- Repair the file path:
vmkfstools -x repair /vmfs/volumes/<datastorepath>/<vm name>/<vm name main base disk>.vmdk
Workaround 2
Disable ATS heartbeat for all hosts.
Refer the article for Disabling ATS heartbeat, ESXi host loses connectivity to a VMFS3 and VMFS5 datastore (2113956)
Workaround 3
Reclaim Disk Space in Horizon
Additional Information
Most other issues with the LookupandOpen[file] can be resolved by following
For more information about troubleshooting VMs which won't power on:
Failed to power on virtual machine
- Powering on a virtual machine fails with the error: File system specific implementation of Ioctl[file] failed
- VM fails to power on with Error: "File system specific implementation of LookupAndOpen [file] failed"
For more information about troubleshooting VMs which won't power on:
Failed to power on virtual machine
Feedback
Yes
No
Powered by
