verify: add requested block information to failure trace
authorFeng, Changyu <Changyu.Feng@emc.com>
Tue, 6 Nov 2018 06:57:27 +0000 (01:57 -0500)
committerJens Axboe <axboe@kernel.dk>
Wed, 7 Nov 2018 04:30:32 +0000 (21:30 -0700)
commit46ff70e8795e91acb2ffc041e6c1fdb4e157dff4
treedc7ad68fb71aa4e88108264b7df6a7e05bc366c1
parent6acc46d8d372638def2f95cb25b2277e0a0b1b0d
verify: add requested block information to failure trace

If verify_interval is not equal to the block size, FIO would verify the
data one segment by one segment according to the verify_interval. The
offset and length in the verify failure trace are the offset and length
of the corrupted segment, not the offset and block size of the IO.

On block storage system, we need the offset and length of the IO to
investigate data corruption issue. For me, I usually search the offset
of the IO in the storage system trace to figure out what happened in the
system.

Fixes: https://github.com/axboe/fio/issues/709
Signed-off-by: Jens Axboe <axboe@kernel.dk>
verify.c