projects
/
fio.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Fix race on io_u->flags
[fio.git]
/
HOWTO
diff --git
a/HOWTO
b/HOWTO
index 662ebe32acf2e10c1956f8f768171da2f92de244..cdd6473b28f3574f7a8eca445715cb3d7156b93e 100644
(file)
--- a/
HOWTO
+++ b/
HOWTO
@@
-811,6
+811,8
@@
verify=str If writing to a file, fio can verify the file contents
sha256 Use sha256 as the checksum function.
sha256 Use sha256 as the checksum function.
+ sha1 Use optimized sha1 as the checksum function.
+
meta Write extra information about each io
(timestamp, block number etc.). The block
number is verified.
meta Write extra information about each io
(timestamp, block number etc.). The block
number is verified.
@@
-821,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
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
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
@@
-840,13
+846,14
@@
verify_interval=int Write the verification header at a finer granularity
size of header_interval. blocksize should divide this
evenly.
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
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
verify_fatal=bool Normally fio will keep checking the entire contents
before quitting on a block verification failure. If this