On Tue, Aug 27, 2013 at 10:02 AM, Jens Axboe <axboe@xxxxxxxxx> wrote: ... >> +data_integrity_check >> + If this option is given, fio will check the i/o number of >> + each block read back during the verification phase. Fio >> + checks numberio to detect stale blocks. Currently, this >> + option requires synchronous i/o, and equal-sized read and >> + write blocks. This option requires workloads that write data. > > I think this use case is just too narrow. Jens. This behavior should be standard behavior for the data integrity checking. To debug data corruption problems we need to know if it's stale data or corrupted data. Huge difference in how to track it down and potential causes. I'm arguing it shouldn't even be an option. > Why does it require sync IO and equal read/write sizes? > Can't you just replay and re-generate and compare? I think it's just limitations of this implementation and testing. In principle I think you are right. Perhaps Juan can explain in more detail. cheers, grant -- 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
