When asynchronous write workloads have the verify option and the verify_state_save option enabled, fio saves the last write completions. Subsequent verify workloads with the verify_state_load option read the saved verify state file. The verify state file stores the last write completions up to the iodepth limit. However, each write may take a longer or shorter time to complete, causing the write completion order to fluctuate. Consequently, the very state file does not always save the last _issued_ writes as many as iodepth. If this occures, the subsequent verify workloads stop unexpectedly without a message, confusing users. This series addresses the problem. The first patch adds a message to inform users why the verify workloads stop. The second patch increases the number of writes saved in the verify state file to reduce the chance of the unexpected stops in verify workloads. The last patch adjusts the test tool "verify-state.c" to the previous patch. Shin'ichiro Kawasaki (3): verify: print message when verify_state_should_stop() returns false verify: double number of writes to save completions t/verify-state.c: adjust to verify state format change backend.c | 12 +++++++++++- fio.h | 1 + io_u.c | 2 +- t/verify-state.c | 8 +++++--- verify-state.h | 9 +++++---- verify.c | 12 ++++++++---- 6 files changed, 31 insertions(+), 13 deletions(-) -- 2.47.0
