“VM1_1-000001-delta.vmdk” is locked in Exclusive mode by host having mac address Looking for lock owners on “VM1_1-000001-delta.vmdk” Username and password for accessing VMware vCenter Server (when tracing MAC address to ESX host.)For example:.To find out the IP address of the host holding the lock, run the /bin/vmfsfilelockinfo Python script.To work around this issue, run the vmfsfilelockinfo script from the host experiencing difficulties with one or more locked files: > There is a manual procedure to locate the host and virtual machine holding locks. These virtual machine files are locked during runtime: The files cannot be accessed by the servers while locked, and the virtual machine is unable to power on. In certain circumstances, these locks may not be released when the virtual machine is powered off. To prevent concurrent changes to critical virtual machine files and file systems, ESXi/ESX hosts establish locks on these files. After you have identified the host or backup tool (machine that owns the MAC) locking the file, power it off or stop the responsible service and then restart the management agents on the host running the virtual machine to release the lock.Įrror : Failed to add disk scsi0:1.The file is locked by a VMkernel child or cartel world and the offending host running the process/world must be rebooted to clear it. In some cases, it may be a Service Console-based lock, an NFS lock, or a lock generated by another system or product that can use or read the VMFS file systems.If the vmkfstools -D test-000001-delta.vmdk command does not return a a valid MAC address in the top field (returns all zeros), review the RO Owner line below it to see which MAC address owns the read only/multi writer lock on the file.To work around this issue in ESX or earlier ESXi releases, Use the vmkfstools -D command to identify the MAC address of the machine locking the file, then reboot or power off the machine that owns that MAC address to release the lock. The ESX host is unable start a virtual machine because there is insufficient disk space to commit changes.Įrror : Failed to lock the file when creating a snapshot Solution : This issue may occur if there is a lack of disk space on the root drive. Review the logs of any third-party software that may have acted on the virtual machine’s VMDK files at the time.Įrror : Failed to get exclusive lock on the configuration file, another VM process could be running, using this configuration file The file may have been locked by third-party software running on an ESXi/ESX host or externally.Info ‘DiskLib’] DISKLIB-VMFS : “/vmfs/volumes/UUID/VMName/Test-000001.vmdk” : closed. When the hostd and vpxa management agents open VMDK descriptor files, they log messages similar to:info ‘DiskLib’] DISKLIB-VMFS : “/vmfs/volumes/UUID/VMName/Test-000001.vmdk” : open successful (21) size = 32227695616, hd = 0.To determine the cause of the previously locked file, review the VMkernel, hostd, and vpxa log files and attempt to determine: If the file is no longer locked, try to power on the virtual machine again. If that application creates and maintains a lock on the required disk files, the virtual machine cannot reopen the file and resume running. During this window, the files could be opened by another virtual machine, management process, or third-party utility. This issue occurs when one of the files required by the virtual machine has been opened by another application.ĭuring a Create or Delete Snapshot operation while a virtual machine is running, all the disk files are momentarily closed and reopened. Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.Ĭannot open the disk ‘/vmfs/volumes/UUID/VMName/Test-000001.vmdk’ or one of the snapshot disks it depends on.
0 Comments
Leave a Reply. |