Hank-Zhao201209

Hi sitsofe, Yes, it's 3.40. OK, we can try your suggestion. Thank you! Does the tool have the limitation of max io tasks in design?

Debian 10.13, kernel: 5.15.152.ve.8-amd64 it's customer own kernel. And this script runs on bare metal, not container or VM.

Yes, this is the script to call the fio script. CASE=$1 TIME=$2 for dev in `lsscsi |grep WUH |awk '{print $6}' |awk -F/ '{print $3}'` do nohup sh ./$CASE $dev...

@sitsofe: After test, it will return fail when the jobs set to 28. [nohup128k16jobsOk.txt](https://github.com/user-attachments/files/21791780/nohup128k16jobsOk.txt) [nohup128k18jobsOk.txt](https://github.com/user-attachments/files/21791784/nohup128k18jobsOk.txt) [nohup128k20jobsOk.txt](https://github.com/user-attachments/files/21791783/nohup128k20jobsOk.txt) [nohup128k24jobsOk.txt](https://github.com/user-attachments/files/21791781/nohup128k24jobsOk.txt) [nohup128k26jobsOk.txt](https://github.com/user-attachments/files/21791782/nohup128k26jobsOk.txt) [nohup128k27jobsOk.txt](https://github.com/user-attachments/files/21791785/nohup128k27jobsOk.txt) [nohup128k28jobsFail.txt](https://github.com/user-attachments/files/21791787/nohup128k28jobsFail.txt) [nohup128k32jobsFail.txt](https://github.com/user-attachments/files/21791786/nohup128k32jobsFail.txt)

Hi @sitsofe , Yes, it's same with you! The only different with you is the message of "libaio.c:443" in fio version 3.40. But this error message is not same with...

@sitsofe the small block(like 4k) and lower iodepth can be successful. but the test sample will use the 128k block with 32 iodepth. Can you help to check root cause...

@sitsofe : The psync ioengine is fail too. And it still fail when the thread=0, and the fio can not runing in the ps -aux. [nohup_thread0_28jobs_fail.txt](https://github.com/user-attachments/files/22035618/nohup_thread0_28jobs_fail.txt) [nohup_psync_28jobs_fail.txt](https://github.com/user-attachments/files/22035620/nohup_psync_28jobs_fail.txt) [psaux_jobs28_thread0_306fioTask.txt](https://github.com/user-attachments/files/22035674/psaux_jobs28_thread0_306fioTask.txt)

This is lest parameter: fio --name=${job_name} --filename=/dev/$DEV --ioengine=libaio --direct=1 --thread=1 --numjobs=28 --iodepth=32 --rw=write --bs=128k --runtime=200 And we found if we change the direct from 1 to 0, the fio can...

Hi @sitsofe : There is no abnormal dmesg print when the command fail. Yes, the "thread" and "ioengine" is not the key parameter, they can be omitted. The message of...

hi @sitsofe : We found the fail message in backend.c -> run_threads() -> fio_sem_down_timeout(), and the 10s timeout is not enough for so much fio task, we change it from...