-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
writefua and readfua may not work with the engine of io_uring #1834
Comments
The |
Dear engineer |
You need to use passthrough with io_uring for that, it won't work with normal file system access. Fio should probably warn about that... |
You will also need to use fio 3.38 for those options. |
Please acknowledge the following before creating a ticket
Description of the bug:
<
Dear engineer
when I use run the command as below, the parameter that writefua and readfua seem not work. There is no fuaflag 0x4000 sent to NVMe SSD . I have some trobule with the usage of fio‘s fua fuction。
fio3.37 --ioengine=io_uring --thread --size=100% --direct=1 --group_reporting --name=test --numjobs=1 --bs=4k --iodepth=1 --writefua=1 --readfua=1 --filename=/dev/nvme0n1 --rw=randwrite --time_based --do_verify=1 -verify_dump=1 --verify_backlog=1 --runtime=21600 --output=a.txt>
Environment: <ubuntu22.04>
fio version: <fio3.37>
Reproduction steps
<fio3.37 --ioengine=io_uring --thread --size=100% --direct=1 --group_reporting --name=test --numjobs=1 --bs=4k --iodepth=1 --writefua=1 --readfua=1 --filename=/dev/nvme0n1 --rw=randwrite --time_based --do_verify=1 -verify_dump=1 --verify_backlog=1 --runtime=21600 --output=a.txt>
The text was updated successfully, but these errors were encountered: