My apologies. Please ignore the previous email. I was using a wrong buffer_pattern in write Usage of --verify=pattern got past the miscompare observed Regards, Gnana On Thu, Jan 4, 2018 at 12:16 AM, Gnana Sekhar <kgsgnana2020@xxxxxxxxx> wrote: > Sure. Agreed. Didn't mean to skip the group, mistakenly hit reply > instead of reply all. Sent the same email again to the mailing list > but received your response around the same time > > 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) > > > Haven't thought of a new mail thread. Good suggestion. Will create a new thread > > Regards, > Gnana > > On Thu, Jan 4, 2018 at 12:03 AM, Sitsofe Wheeler <sitsofe@xxxxxxxxx> wrote: >> Hi, >> >> Can you ensure fio questions are sent to the mailing list and not just >> me? Others often benefit from the answers when using search engines >> and it gives people other than myself a chance to answer your question >> too! :-) >> >> The value of verify_pattern is only used when verify=pattern (see >> http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-verify >> ) is set. It's interesting that you got a verifying run without that >> option though :-) Also note you can arrange for runs with verify >> options to only do the write part by using do_verify=0 (see >> http://fio.readthedocs.io/en/latest/fio_doc.html#cmdoption-arg-do-verify >> ). >> >> (PS: it would have also been nicer to have started a new mail thread >> for this continue the existing one) >> >> On 4 January 2018 at 06:44, Gnana Sekhar <kgsgnana2020@xxxxxxxxx> wrote: >>> >>> I am running into error in verify after I do a write and verify. I am >>> running these commands from the shell and not in parallel. Below are >>> the parameters I am passing to FIO >>> Please let me know if you find something obvious >>> >>> $ 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=1 --size=76815 >>> >>> >>> $ 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=76815 --rw=read >>> --verify_pattern=0x1 --debug=all >>> >>> verify: bad magic header 101, wanted acca at file /dev/nvme0n1 offset >>> 0, length 4096 >> >> -- >> 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
