X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=cdd6473b28f3574f7a8eca445715cb3d7156b93e;hp=eb8f453ca309b156d279ce1c7a678cefccb6eb6b;hb=daaa166fb4d4869882885094d8b8ad44f6d159ce;hpb=23d2461974c334d77eb7a06a2dbd1f37aeee85d4

diff --git a/HOWTO b/HOWTO
index eb8f453c..cdd6473b 100644
--- a/HOWTO
+++ b/HOWTO
@@ -823,7 +823,11 @@ verify=str	If writing to a file, fio can verify the file contents
 
 		This option can be used for repeated burn-in tests of a
 		system to make sure that the written data is also
-		correctly read back.
+		correctly read back. If the data direction given is
+		a read or random read, fio will assume that it should
+		verify a previously written file. If the data direction
+		includes any form of write, the verify will be of the
+		newly written data.
 
 verifysort=bool	If set, fio will sort written verify blocks when it deems
 		it faster to read them back in a sorted manner. This is
@@ -842,13 +846,14 @@ verify_interval=int	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
+verify_pattern=str	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.
+		buffer at the time(it can be either a decimal or a hex number).
+		The verify_pattern if larger than a 32-bit quantity has to
+		be a hex number that starts with either "0x" or "0X".
 
 verify_fatal=bool	Normally fio will keep checking the entire contents
 		before quitting on a block verification failure. If this