I started seeing the following whines from emulated nvme on vmware workstation some time ago, and it seems to happen almost exclusively during the nightly periodic run:
Jul 3 03:01:47 titan kernel: nvme0: RECOVERY_START 48053105730250 vs 48051555254036 Jul 3 03:01:47 titan kernel: nvme0: timeout with nothing complete, resetting Jul 3 03:01:47 titan kernel: nvme0: Resetting controller due to a timeout. Jul 3 03:01:47 titan kernel: nvme0: RECOVERY_WAITING Jul 3 03:01:47 titan kernel: nvme0: resetting controller Jul 3 03:01:47 titan kernel: nvme0: temperature threshold not supported Jul 3 03:01:47 titan kernel: nvme0: resubmitting queued i/o Jul 3 03:01:47 titan kernel: nvme0: READ sqid:10 cid:0 nsid:1 lba:8931648 len:8 Jul 3 03:01:47 titan kernel: nvme0: aborting outstanding i/o Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_START 48207341204759 vs 48207032791553 Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_START 48207722834338 vs 48207032791553 Jul 3 03:02:23 titan kernel: nvme0: timeout with nothing complete, resetting Jul 3 03:02:23 titan kernel: nvme0: Resetting controller due to a timeout. Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_WAITING Jul 3 03:02:23 titan kernel: nvme0: resetting controller Jul 3 03:02:23 titan kernel: nvme0: temperature threshold not supported Jul 3 03:02:23 titan kernel: nvme0: aborting outstanding i/o Jul 3 03:02:23 titan kernel: nvme0: resubmitting queued i/o Jul 3 03:02:23 titan kernel: nvme0: WRITE sqid:1 cid:0 nsid:1 lba:27806528 len:8 Jul 3 03:02:23 titan kernel: nvme0: aborting outstanding i/o It does not seem to break anything, i.e. no errors from periodic, zpool status and zpool scrub do not show any issues as well, so I'm just wondering if there is some obvious reason for this. I am staying current with, well, -CURRENT and VMware Workstation versions (now at 16.2.3), and do not remember when exactly this started. There are no other VMs doing anything at that time, host system is pretty idle as well.
