strange logs on esxi server

[imidb]

Hello, there are a lot of logs in wmkwarning.log like these:

WARNING: Fil3: 4267: 'datastore2a-R5': AFF_OPEN_PATH: <FD c27 r22>: total wait 13 ms: Success

It is a standalone esxi server with local SSD disks.

Is this important? How can I fix this?

[kastlr]

Hi,

which ESXi Version do you use?

Might be a good idea to check also the vmkernel,log file as it usually contains more details compared to the vmkwarning.log.

[imidb]

Hi @kastlr 

esxi 7.0 u3 version.

these logs from vmkernel.log in same time

Spoiler

2023-09-13T23:28:15.332Z cpu20:12817667 opID=79181fc6)World: 12077: VC opID 16e4c774 maps to vmkernel opID 79181fc6
2023-09-13T23:28:15.332Z cpu20:12817667 opID=79181fc6)WARNING: Fil3: 4267: 'datastore2-R5': AFF_OPEN_PATH: <FD c10 r14>: total wait 10 ms: Success
2023-09-13T23:28:15.333Z cpu20:12817667 opID=79181fc6)FDS: 643: Enabling IO coalescing on driver 'deltadisks' device '30699aaa-vps-000001-sesparse.vmdk'
2023-09-13T23:28:15.337Z cpu20:12817667 opID=79181fc6)CBT: 1346: Created device 2bed9ac3-cbt for cbt driver with filehandle 736991939
2023-09-13T23:28:15.399Z cpu20:12817667 opID=79181fc6)CBT: 1346: Created device 29bc9aee-cbt for cbt driver with filehandle 700226286
2023-09-13T23:28:15.417Z cpu20:12817667 opID=79181fc6)CBT: 727: Disconnecting the cbt device 2bed9ac3-cbt with filehandle 736991939
2023-09-13T23:28:15.435Z cpu20:12817667 opID=79181fc6)CBT: 727: Disconnecting the cbt device 29bc9aee-cbt with filehandle 700226286
2023-09-13T23:28:15.438Z cpu20:12817667 opID=79181fc6)FDS: 643: Enabling IO coalescing on driver 'deltadisks' device '30699aaa-vps-000001-sesparse.vmdk'
2023-09-13T23:28:15.438Z cpu20:12817667 opID=79181fc6)CBT: 1346: Created device 2bef9ac3-cbt for cbt driver with filehandle 737123011
2023-09-13T23:28:15.456Z cpu20:12817667 opID=79181fc6)SVM: 5105: SkipZero 0, dstFsBlockSize -1, preallocateBlocks 0, vmfsOptimizations 0, useBitmapCopy 1, skipPlugGrain 1, destination disk grainSize 0
2023-09-13T23:28:15.456Z cpu20:12817667 opID=79181fc6)SVM: 5199: SVM_MakeDev.5199: Creating device 2bef9ac3-29bc9aee-svmmirror: Success
2023-09-13T23:28:15.456Z cpu20:12817667 opID=79181fc6)SVM: 5252: Created device 2bef9ac3-29bc9aee-svmmirror, primary 2bef9ac3, secondary 29bc9aee
2023-09-13T23:28:15.457Z cpu20:12817667 opID=79181fc6)VSCSI: 4752: handle 55051413331396680(GID:18504)(vscsi0:0):Creating Virtual Device for world 12817656 (FSS handle 785423045) numBlocks=1048576000 (bs=512)
2023-09-13T23:28:15.457Z cpu20:12817667 opID=79181fc6)VSCSI: 273: handle 55051413331396680(GID:18504)(vscsi0:0):Input values: res=0 limit=-2 bw=-1 Shares=1000
2023-09-13T23:28:15.457Z cpu20:12817667 opID=79181fc6)Vmxnet3: 14064: indLROPktToGuest: 1, vcd->umkShared->vrrsSelected: 4 port 0x6000029
2023-09-13T23:28:15.457Z cpu20:12817667 opID=79181fc6)Vmxnet3: 14331: Using default queue delivery for vmxnet3 for port 0x6000029
2023-09-13T23:28:15.457Z cpu20:12817667 opID=79181fc6)Vmxnet3: 1727: UPT feature is disabled.

[kastlr]

Hi,

that message seems to be related to snapshot creation/consolidation.

It's also mentioned here.

PR 2851811: Virtual machines might stop to respond during power on or snapshot consolidation operati...

So it does looks like your scenario isn't handled by the fix included in 7.0 U3d, so I would recommend to open a ticket with VMware and refer to PR 2851811.