View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000634 | AlmaLinux-10 | General | public | 2026-06-18 09:47 | 2026-06-18 10:13 |
| Reporter | vikidia | Assigned To | |||
| Priority | high | Severity | crash | Reproducibility | random |
| Status | new | Resolution | open | ||
| Summary | 0000634: Disk I/O issue in Proxmox VM (Aborted Command) + XFS shut down | ||||
| Description | Following this thread : https://forum.proxmox.com/threads/io_uring-on-kernel-7-0-6-2-pve-pve-9-2-3-guest-disk-i-o-errors-eio-filesystem-xfs-shutdown.184360/ I discovered a strange behavior on AlmaLinux 10 inside a Proxmox VM. It appears that kernel 6.12.0-211.22.1.el10_2.x86_64 has issue that triggers a disk failure (see screenshots). Randomly, the filesystem (XFS) becomes unavailable and I can't do anything more except stop and start the VM again. I don't know if it's related to the storage architecture on Proxmox but I'm using LUKS + LVM-thin on 2 different hosts that are impacted. Here is the way I was able to reproduce : 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 --group_reporting \ --filename=/tmp/fio-test --output-format=normal,json \ --output=fio-result.json Jobs: 8 (f=0): [/(8)][-.-%][eta 10m:15s] Jobs: 8 (f=0): [/(8)][-.-%][eta 10m:15s] Jobs: 8 (f=0): [/(8)][-.-%][eta 10m:14s] fio: io_u error on file /tmp/fio-test: Input/output error: write offset=20592291840, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=9765498880, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=11389923328, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=10865082368, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=4592693248, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=17240551424, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=10608463872, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=18193764352, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=10405310464, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=18420568064, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=20068622336, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=14732562432, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=19714949120, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=11894398976, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=13342396416, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=18269777920, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=21153767424, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=8210624512, buflen=4096 fio: io_u error on file /tmp/fio-test: Input/output error: write offset=5009162240, buflen=4096 | ||||
| Steps To Reproduce | Use last proxmox version (kernel 7.0.6-2-pve + PVE 9.2.3) Maybe use LUKS and LVM-thin as storage type for the VM Install AlmaLinux 10 with XFS and kernel 6.12.0-211.22.1.el10_2.x86_64 (in a VM) Do a FIO stress write test : 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 --group_reporting --filename=/tmp/fio-test --output-format=normal,json --output=fio-result.json | ||||
| Tags | disk, I/O failure, LVM-thin, Proxmox, VM, xfs | ||||
| Attached Files | |||||
|
|
No issue in logs found in Proxmox hypervisor physical hosts. The issue appears in 2 different Proxmox hosts. The AlmaLinux kernel 6.12.0-124.52.1.el10_1.x86_64 does not seem to be impacted, |
|
|
This command also triggers the problem : fio --name=stress-hdd --ioengine=libaio --iodepth=8 --rw=randwrite \ --bs=4k --direct=1 --fdatasync=8 --size=20G --numjobs=4 \ --runtime=1800 --time_based --ramp_time=30 --group_reporting \ --filename=/tmp/fio-test --output-format=normal,json \ --output=fio-result.json |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-06-18 09:47 | vikidia | New Issue | |
| 2026-06-18 09:47 | vikidia | Tag Attached: xfs | |
| 2026-06-18 09:47 | vikidia | File Added: image.png | |
| 2026-06-18 09:47 | vikidia | File Added: image-2.png | |
| 2026-06-18 09:47 | vikidia | File Added: image-3.png | |
| 2026-06-18 09:49 | vikidia | Tag Attached: disk | |
| 2026-06-18 09:49 | vikidia | Tag Attached: I/O failure | |
| 2026-06-18 09:49 | vikidia | Tag Attached: VM | |
| 2026-06-18 09:49 | vikidia | Tag Attached: Proxmox | |
| 2026-06-18 09:49 | vikidia | Tag Attached: LVM-thin | |
| 2026-06-18 09:51 | vikidia | Note Added: 0001223 | |
| 2026-06-18 10:13 | vikidia | Note Added: 0001224 |