to repeat the same workload a given number of times. Defaults
to 1.
+do_verify=bool Run the verify phase after a write phase. Only makes sense if
+ verify is set. Defaults to 1.
+
verify=str If writing to a file, fio can verify the file contents
after each iteration of the job. The allowed values are:
crc7 Use a crc7 sum of the data area and store
it in the header of each block.
+ sha512 Use sha512 as the checksum function.
+
+ sha256 Use sha256 as the checksum function.
+
+ meta Write extra information about each io
+ (timestamp, block number etc.). The block
+ number is verified.
+
+ pattern Fill the IO buffers with a specific pattern,
+ that we can use to verify. Depending on the
+ width of the pattern, fio will fill 1/2/3/4
+ bytes of the buffer at the time. The pattern
+ cannot be larger than a 32-bit quantity. The
+ given pattern is given as a postfix to this
+ option, ala: verify=pattern:0x5a. It accepts
+ both hex and dec values.
+
null Only pretend to verify. Useful for testing
internals with ioengine=null, not for much
else.
than the blocksize. It will be written for chunks the
size of header_interval. blocksize should divide this
evenly.
+
+verify_fatal=bool Normally fio will keep checking the entire contents
+ before quitting on a block verification failure. If this
+ option is set, fio will exit the job on the first observed
+ failure.
stonewall Wait for preceeding jobs in the job file to exit, before
starting this one. Can be used to insert serialization