buffer_pattern=0 but verify_pattern=0x1 - are you sure you want them to be different? On 4 January 2018 at 07:16, Gnana Sekhar <kgsgnana2020@xxxxxxxxx> wrote: > > Even with addition of --verify=pattern, I step into the failure > > $ sudo fio --thread --direct=1 --minimal --ioengine=libaio --numjobs=1 > --iodepth=1 --name=bs128k_rwread_rsmixr0_qd256 --bs=4096 > --percentage_random=0 --rw=write --filename=/dev/nvme0n1 -o > /home/temp.log --buffer_pattern=0 --size=409600 > > > $ sudo fio --thread --direct=1 --minimal --ioengine=libaio --numjobs=1 > --iodepth=1 --bs=4096 --percentage_random=0 --filename=/dev/nvme0n1 -o > /home/temp.log --name=bs4096_rwverify_qd256 --size=409600 --rw=read > --verify_pattern=0x1 --verify=pattern > fio: got pattern '00', wanted '01'. Bad bits 1 > fio: bad pattern block offset 0 > pattern: verify failed at file /dev/nvme0n1 offset 0, length 0 > fio: verify type mismatch (0 media, 18 given) -- 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
