If I remembered correctly, the fio sometimes showed V status. I have set read verify with verify_async enabled and the fio always showed V status. 2016-03-25 23:10 GMT+08:00 Jens Axboe <axboe@xxxxxxxxx>: > On 03/25/2016 09:03 AM, flash yan wrote: >> >> I have tried your patch. It fixed the issue. But I don't understand >> "So we just kept piling on buffers to verify, but we never did". >> You mean that fio didn't run any verify job with verify_async enabled? > > > Right, it did not for your case. But that's because of the super short loop > and the time_based setup, otherwise it would have. That was apparent while > it was running too (not reads or V status), and in the final output (no > reads there either). So it was a corner case where verify did not happen, > since the referenced commit that broke it for that case. > > -- > Jens Axboe > -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
