+
+verify_dump=bool If set, dump the contents of both the original data
+ block and the data block we read off disk to files. This
+ allows later analysis to inspect just what kind of data
+ corruption occurred. On by default.
+
+verify_async=int Fio will normally verify IO inline from the submitting
+ thread. This option takes an integer describing how many
+ async offload threads to create for IO verification instead,
+ causing fio to offload the duty of verifying IO contents
+ to one or more separate threads. If using this offload
+ option, even sync IO engines can benefit from using an
+ iodepth setting higher than 1, as it allows them to have
+ IO in flight while verifies are running.
+
+verify_async_cpus=str Tell fio to set the given CPU affinity on the
+ async IO verification threads. See cpus_allowed for the
+ format used.
+
+verify_backlog=int Fio will normally verify the written contents of a
+ job that utilizes verify once that job has completed. In
+ other words, everything is written then everything is read
+ back and verified. You may want to verify continually
+ instead for a variety of reasons. Fio stores the meta data
+ associated with an IO block in memory, so for large
+ verify workloads, quite a bit of memory would be used up
+ holding this meta data. If this option is enabled, fio
+ will write only N blocks before verifying these blocks.
+
+ will verify the previously written blocks before continuing
+ to write new ones.
+
+verify_backlog_batch=int Control how many blocks fio will verify
+ if verify_backlog is set. If not set, will default to
+ the value of verify_backlog (meaning the entire queue
+ is read back and verified). If verify_backlog_batch is
+ less than verify_backlog then not all blocks will be verified,
+ if verify_backlog_batch is larger than verify_backlog, some
+ blocks will be verified more than once.