On 07/09/2024 00:29, Luis Chamberlain wrote:
On Fri, Sep 06, 2024 at 04:22:24PM +0100, John Garry wrote:
However, if we have multiple jobs, they may overwrite blocks from other jobs
- fio warns us about that. As such, in verify mode, the read sequence number
may not match was we were expecting with multiple jobs running.
Is that a generic bug in fio?
I wouldn't say so. That is just how the verify mode works.
Fundamentally verify mode is to verify that we read back the contents of
the file as expected after each iteration. If some other job comes along
and overwrites that data, then that cannot be helped.
However maybe I should just create a new verify mode for atomic writes,
so it is clear what the verify operation constraints are.
Thanks,
John
