On Tue, May 12, 2015 at 9:49 AM, Alireza Haghdoost <haghdoost@xxxxxxxxx> wrote: > I want to do following experiment with FIO but now sure FIO have this > capability in place: > > 1. Run FIO and write a random content pattern on a RAW device or a File. > 2. Run FIO and verify the contents that has been written is correct. > > Based on my understanding, FIO do the verification phase at the same > run instance. However, I want the verification phase happen in a > separate stand alone run instance that may happen later. > > Would you please kindly let me know if this capability is available ? > If not, I will appreciate your input so I can expand the toolset. > > Thanks > -- > 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 One of the example job files sounds similar to what you're asking for. It uses a two phase approach, write phase, then verify phase. I modified it a bit but maybe it will help you get on the right track. ; writes 512 byte verification blocks until the disk is full, ; then verifies written data [global] thread=1 bs=128k direct=1 ioengine=sync verify=meta verify_pattern=0x0123456789abcdef verify_interval=512 [write-phase] filename=${fname} ; or use a full disk, for example /dev/sda rw=write fill_device=1 do_verify=0 [verify-phase] stonewall create_serialize=0 filename=${fname} rw=read do_verify=1 -- 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
