nrfiles vs nr_files mixups

[fio.git] / fio.1

diff --git a/fio.1 b/fio.1
index 9ca38abcdc6c69e48f39ec6c7c1b9d03a1baa3f8..b0276c4cfb17f7b5cc33daa30e23a324d9a1b5c8 100644 (file)
--- a/fio.1
+++ b/fio.1
@@ -226,7 +226,7 @@ are likely to be issued. Default: true.
 .BI size \fR=\fPint
 Total size of I/O for this job.  \fBfio\fR will run until this many bytes have
 been transfered, unless limited by other options (\fBruntime\fR, for instance).
-Unless \fBnr_files\fR and \fBfilesize\fR options are given, this amount will be
+Unless \fBnrfiles\fR and \fBfilesize\fR options are given, this amount will be
 divided between the available files for the job. If not set, fio will use the
 full size of the given files or devices. If the the files do not exist, size
 must be given.
@@ -698,13 +698,16 @@ 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 verify
-the previously written blocks before continuing to write new ones.
+be used up holding this meta data. If this option is enabled, fio will write
+only N blocks before verifying these blocks.
 .TP
 .BI verify_backlog_batch \fR=\fPint
 Control how many blocks fio will verify if verify_backlog is set. If not set,
 will default to the value of \fBverify_backlog\fR (meaning the entire queue is
-read back and verified).
+read back and verified).  If \fBverify_backlog_batch\fR is less than 
+\fBverify_backlog\fR then not all blocks will be verified,  if 
+\fBverify_backlog_batch\fR is larger than \fBverify_backlog\fR,  some blocks
+will be verified more than once.
 .TP
 .B stonewall
 Wait for preceeding jobs in the job file to exit before starting this one.