On Thu, 13 Feb 2025 14:25:07 +0900, Shin'ichiro Kawasaki wrote:
> 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.
>
> [...]
Applied, thanks!
[1/3] verify: print message when verify_state_should_stop() returns false
commit: ceb624e812ea20316532516f1422211fe6ea8bd3
[2/3] verify: double number of writes to save completions
commit: 9abce429d3211add643229a593d0b028b51f5942
[3/3] t/verify-state.c: adjust to verify state format change
commit: 0e0d9a3a3a0aec52836d32d749d4f838b673d73c
Best regards,
--
Jens Axboe
