X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=d185f8a2944a36d3c45ad33810cdc9dd42c56bd2;hp=cdfe80aa9fc4f1908ecf504a9ba5dae1b7a11071;hb=4241ea8fb0606f9bd5b7ed1278d3b7825883acf6;hpb=e84c73a89ef19f38e117ed4fae5eb3bd4aee8a81

diff --git a/HOWTO b/HOWTO
index cdfe80aa..d185f8a2 100644
--- a/HOWTO
+++ b/HOWTO
@@ -569,7 +569,7 @@ loops=int	Run the specified number of iterations of this job. Used
 		to repeat the same workload a given number of times. Defaults
 		to 1.
 
-do_verify=int	Run the verify phase after a write phase. Only makes sense if
+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
@@ -599,6 +599,15 @@ verify=str	If writing to a file, fio can verify the file contents
 				(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.
@@ -624,13 +633,10 @@ verify_interval=siint	Write the verification header at a finer granularity
 			size of header_interval. blocksize should divide this
 			evenly.
 
-verify_pattern=int	If set, fio will fill the io buffers with this
-		pattern. Fio defaults to filling with totally random
-		bytes, but sometimes it's interesting to fill with a known
-		pattern for io verification purposes. Depending on the
-		width of the pattern, fio will fill 1/2/3/4 bytes of the
-		buffer at the time. The verify_pattern cannot be larger than
-		a 32-bit quantity.
+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
@@ -750,7 +756,7 @@ Client1 (g=0): err= 0:
     slat (msec): min=    0, max=  136, avg= 0.03, stdev= 1.92
     clat (msec): min=    0, max=  631, avg=48.50, stdev=86.82
     bw (KiB/s) : min=    0, max= 1196, per=51.00%, avg=664.02, stdev=681.68
-  cpu        : usr=1.49%, sys=0.25%, ctx=7969
+  cpu        : usr=1.49%, sys=0.25%, ctx=7969, majf=0, minf=17
   IO depths    : 1=0.1%, 2=0.3%, 4=0.5%, 8=99.0%, 16=0.0%, 32=0.0%, >32=0.0%
      issued r/w: total=0/32768, short=0/0
      lat (msec): 2=1.6%, 4=0.0%, 10=3.2%, 20=12.8%, 50=38.4%, 100=24.8%,
@@ -781,7 +787,9 @@ runt=		The runtime of that thread
 		only really useful if the threads in this group are on the
 		same disk, since they are then competing for disk access.
 cpu=		CPU usage. User and system time, along with the number
-		of context switches this thread went through.
+		of context switches this thread went through, usage of
+		system and user time, and finally the number of major
+		and minor page faults.
 IO depths=	The distribution of io depths over the job life time. The
 		numbers are divided into powers of 2, so for example the
 		16= entries includes depths up to that value but higher