Hi, On 31 March 2017 at 03:25, Guruganesh Hegde <guruhegde4u@xxxxxxxxx> wrote: > > I am using fio version 2.12 and using following configuration to > perform data integrity check > -------------------------------------------------------------------- > [write-phase] > group_reporting > rw=randwrite > bs=4k > direct=1 > ioengine=libaio > > iodepth=32 > numjobs=1 > > size=32G > randseed=40964096 > verify=crc32c > > verify_dump=1 > refill_buffers > > filename=/dev/nvme0n1 > > loops=10 > ---------------------------------------------------------------------------------- > > What I am seeing is fio fails for numberio with mismatch. > "verify: bad header numberio x wanted y" > > I have modified fio 'verify.c' to continue on numberio mismatch error. > All other header checks like header crc & data crcs are verified. > > After the above changes fio reports only few numberio errors and there > seem to no other data integrity error. > > Is there anything I am missing in fio configuration? On first glance the config looks fine. refill_buffers is actually automatically set when you set verify (see http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-refill-buffers ) so it's redundant but harmless and won't have anything to do with the error you reported. A few suggestions: Can you reproduce the problem with the latest fio release (2.18)? Can you make it happen with size=1G ? If so how about size=256M ? How far does it get through the total I/O before the numberio problem is shown (i.e. what output is displayed when failure occurs and fio exits) and is it roughly the same amount each time? Does everything else still verify when you use bsrange=4k-64k instead of bs=4k? -- Sitsofe | http://sucs.org/~sits/ -- 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
