IoTracker reports significant delay /var/run/log/hostd.log
YYY-MM-DDTHH:MM:SS warning hostd[2102015] [Originator@6876 sub=IoTracker opID=ID] In thread 2101986, access("/vmfs/volumes/<datastore>/VMfolder/hbr-persistent-state-RDID-<id>.psf") took over 2108 sec.vmware.log /vmfs/volumes/datastore/VM/vmware.logYYYY-MM-DDTHH:MM:SS In(05) vmx - VigorTransportProcessClientPayload: opID=<opID> seq=621882: Receiving Snapshot.Take request.YYYY-MM-DDTHH:MM:SS In(05) vmx - SnapshotVMX_TakeSnapshot start: 'Backup Snapshot', deviceState=0, lazy=0, quiesced=1, forceNative=0, tryNative=1, saveAllocMaps=0YYYY-MM-DDTHH:MM:SS In(05) vmx - VVolObjNotifySnapshotPrepare: Changing state to VEC_SNAP_PREPARE_IN_PROG.YYYY-MM-DDTHH:MM:SS In(05) vmx - SNAPSHOT: SnapshotPrepareTakeDoneCB: Prepare phase complete (The operation completed successfully).YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - Destroying virtual dev for scsi0:0 vscsi=198494314471380343YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - VMMon_VSCSIStopVports: No such target on adapterYYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - Destroying virtual dev for scsi0:1 vscsi=198494314475574648YYYY-MM-DDTHH:MM:SS In(05) vcpu-0 - VMMon_VSCSIStopVports: No such target on adapterYYYY-MM-DDTHH:MM:SS Wa(03) vmx - Caught signal 15 -- tid 9327572 (eip 0x691b6c7e23)
Thread ID 9327572 matches below in vmkernelvmkernel.log/var/run/log/vmkernel.log YYYY-MM-DDTHH:MM:SS cpu170:9327572 opID=867dd7be)World: 12077: VC opID 49d78647-2d-f32f maps to vmkernel opID 867dd7beYYYY-MM-DDTHH:MM:SS cpu170:9327572 opID=867dd7be)SVM: 5095: SkipZero 0, dstFsBlockSize 0, preallocateBlocks 0, vmfsOptimizations 1, useBitmapCopy 0,YYYY-MM-DDTHH:MM:SS cpu168:9327572 opID=867dd7be)SVM: 5095: SkipZero 0, dstFsBlockSize 0, preallocateBlocks 0, vmfsOptimizations 1, useBitmapCopy 0, skipPlugGrain 0, destination disk grainSize 0YYYY-MM-DDTHH:MM:SS cpu168:9327572 opID=867dd7be)SVM: 5189: SVM_MakeDev.5189: Creating device 1ea3b886-1c0533c5-cbtmirror: SuccessYYYY-MM-DDTHH:MM:SS cpu168:9327572 opID=867dd7be)SVM: 5242: Created device 1ea3b886-1c0533c5-cbtmirror, primary 1ea3b886, secondary 1c0533c5This issue is seen since multiple threads can come simultaneously for allocating blocks on thin disk files
This issue is resolved in VMware ESXi 7.0 Update 3i Release. Log in to the Broadcom Support Portal to download this patch
There is no workaround.