you could either write out '4096' or just give 4k. The postfixes
signify base 2 values, so 1024 is 1k and 1024k is 1m and so on.
If the option accepts an upper and lower range, use a colon ':'
- or minus '-' to separate such values. See irange.
+ or minus '-' to separate such values. May also include a prefix
+ to indicate numbers base. If 0x is used, the number is assumed to
+ be hexadecimal. See irange.
bool Boolean. Usually parsed as an integer, however only defined for
true and false (1 and 0).
irange Integer range with postfix. Allows value range to be given, such
roundrobin Round robin over open files. This
is the default.
+ sequential Finish one file before moving on to
+ the next. Multiple files can still be
+ open depending on 'openfiles'.
+
The string can have a number appended, indicating how
often to switch to a new file. So if option random:4 is
given, fio will switch to a new random file after 4 ios
new random offset without looking at past io history. This
means that some blocks may not be read or written, and that
some blocks may be read/written more than once. This option
- is mutually exclusive with verify= for that reason, since
- fio doesn't track potential block rewrites which may alter
- the calculated checksum for that block.
+ is mutually exclusive with verify= if and only if multiple
+ blocksizes (via bsrange=) are used, since fio only tracks
+ complete rewrites of blocks.
softrandommap See norandommap. If fio runs with the random block map enabled
and it fails to allocate the map, if this option is set it
create_fsync=bool fsync the data file after creation. This is the
default.
+create_on_open=bool Don't pre-setup the files for IO, just create open()
+ when it's time to do IO to that file.
+
unlink=bool Unlink the job files when done. Not the default, as repeated
runs of that job would then waste time recreating the file
set again and again.