Skip to main content

ESXi hostd log spew post VM backup: Block list: Cannot convert disk path (path to vmdk> to real path, skipping.

  Symptoms

  • After the daily VM backup, you notice that one or more ESXi hosts report the below log spew continuously in the /var/log/hostd.log
2020-05-28T01:17:20.907Z warning hostd[2100454] [Originator@6876 sub=Default opID=56ff9f3f-75-f610 user=vpxuser:testdomain\testuser] Block list: Cannot convert disk path /vmfs/volumes/2622ebd8-4b853593/TESTVM/TESTVM-000002.vmdk (/vmfs/volumes/2622ebd8-4b853593/TESTVM/TESTVM-000002.vmdk) to real path, skipping.
  •  In ESXI - /var/log/vpxa.log  reports the below errors during this issue
[context]zKq7AVICAgAAAKBJ9QAZdnB4YQAALE42bGlidm1hY29yZS5zbwAAsL4bAJCcFwHPyP5saWJ2aW0tdHlwZXMuc28AgSLWFwGBgrkTAQK6OQ1saWJ2bW9taS5zbwACbIgRAmeNEQPuQyd2cHhhAANIRicCRbATgcbEMwEDydUvBH7uCWxpYnZweGFwaS10eXBlcy5zbwADrt83A4E+JwO46TYDxvc2A2JNNwC15SgAk+koAKvENgU7fQBsaWJwdGhyZWFkLnNvLjAABn2fDmxpYmMuc28uNgA=[/context]' received while invoking acquireLeaseExt on vim.host.DiskManager:ha-blklist-service
2020-05-28T01:16:10.891Z error vpxa[2108445] [Originator@6876 sub=SoapAdapter opID=7f722a82-41] Method vpxapi.VpxaService.AcquireDiskManagerLeaseExt threw undeclared fault of type vim.fault.LeaseFault
2020-05-28T01:16:10.943Z error vpxa[2100302] [Originator@6876 sub=vpxaVmomi opID=5b1342da-f5] [VpxaClientAdapter::InvokeCommon] Re-throwing method-fault 'N3Vim5Fault10LeaseFault9ExceptionE(Fault cause: vim.fault.LeaseFault
  •  If you are logging to a remote syslog server, you might see the syslog file growing to very large size and might fill up the disk space.
  •  The vmdk referenced in the above message does not exist.
Cause
Due to a race condition in the snapshot consolidation workflow.
Impact / Risks
No impact in restarting the management agents.
Resolution
This is a known issue. Currently there is no resolution.

Workaround
Restart the "hostd" agent on the ESXi host

Comments

Post a Comment

Popular posts from this blog

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased. List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose Note : Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0. List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose   List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose Note : This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full. ...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more