FIO IO is not continuous post trigger-timeout cmd execution, even specified runtime is higher.

[sathish356]

Please acknowledge the following before creating a ticket

• [x] I have read the GitHub issues section of REPORTING-BUGS.

Description of the bug: When i try to run fio cmd with runtime and trigger-timeout, I am not seeing any continuous I/O post trigger cmd execution, IO stopped at trigger-timeout.

For example, I am planning to run 300s IO and try to execute hostname cmd using trigger param at trigger-timeout value as 5s, in this cas, I am able to see only IO until 5s trigger-timeout not 300s runtime.

I believe IO should continue until specified runtime.

Environment: Linux 5.6.13

fio version: fio-3.19

Reproduction steps step1: date step2: fio --name=ran --filename=/dev/nvme1n1 --rw=read --time_based --runtime 300s --numjobs=2 --trigger-timeout 5s --trigger="hostname;sleep 10s" step3: date Result fio IO completed in 5s instead of 300s runtime.

[sitsofe]

@sathish356 The code backs up what you're saying... If you look at

• https://github.com/axboe/fio/blob/fio-3.27/backend.c#L2146-L2153
• https://github.com/axboe/fio/blob/fio-3.27/server.c#L959-L978

you will see that fio tells running threads to terminate after a trigger goes off and before it even execs the trigger command. At a bare minimum the documentation could be updated to make this behaviour clearer... Would you like to submit a documentation improvement?

[sathish356]

Ok