We hit the same signature across VMs with different guest kernels and across different nodes of 1 cluster:
- Ubuntu 22.04.5, kernel 5.15.0-181 (XFS data disks fail; ext4 root survives)
- RHEL 8.10, kernel 4.18.0-553 (XFS)
Host:
- Proxmox VE...
Upgraded to proxmox 9.2.10 on Sunday September the 6th.
Have had two downtimes of a host because of that since.
Both downtimes occurred during the Proxmox Backup of some other machines which places an extra burden on the physical disks. And in...
By the way, I also reproduced the issue on AlmaLinux 10.1 (kernel 6.12.0-124.52.1.el10_1.x86_64) with this command :
fio --name=stress-hdd --ioengine=libaio --iodepth=8 --rw=randwrite \
--bs=4k --direct=1 --fdatasync=8 --size=20G --numjobs=4...
I now have seen this behavior, too, but with ZFS on the PVE host and both ext4 and ZFS on the VM guests. The machine is equipped with SSD-only, 6 NVME, 2 SATA. All of them are in three ZFS mirror pools (one with 2x NVME, one with 4 and the last...
The problem is also triggered on last kernel 7.0.12-1-pve.
[root@patchmon ~]# fio --name=stress-hdd --ioengine=libaio --iodepth=8 --rw=randwrite --bs=4k --direct=1 --fdatasync=8 --size=20G --numjobs=8
--runtime=1800 --time_based...
Some news :
I was able to reboot one of the both Proxmox host on Kernel 6.17.13-13-pve and retry the same process / same stress write test (30 minutes of stress).
I confirm that there is no issue on this kernel version.
So it seems to be a...
I just find a way to reproduce the issue on the guest :
root@zabbix :~$ fio --name=stress-write --ioengine=libaio --iodepth=64 --rw=randwrite \
--bs=4k --direct=1 --size=20G --numjobs=8 --runtime=600 \
--time_based --ramp_time=30...