X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=f323c204d3c67be97e98926ae8efd0ae1d82314d;hp=8f7320835c914ea54820a4b35330a8cb2d06205d;hb=5f9099ea8adf423d0db01274ef0d7e65629c0e1c;hpb=1621031e8a7cbb91afad124da405fc4eabda764f

diff --git a/HOWTO b/HOWTO
index 8f732083..f323c204 100644
--- a/HOWTO
+++ b/HOWTO
@@ -314,7 +314,8 @@ filesize=int	Individual file sizes. May be a range, in which case fio
 
 fill_device=bool Sets size to something really large and waits for ENOSPC (no
 		space left on device) as the terminating condition. Only makes
-                sense with sequential write.
+                sense with sequential write. For a read workload, the mount
+		point will be filled first then IO started on the result.
 
 blocksize=int
 bs=int		The block size used for the io units. Defaults to 4k. Values
@@ -529,6 +530,9 @@ fsync=int	If writing to a file, issue a sync of the dirty data
 		not sync the file. The exception is the sg io engine, which
 		synchronizes the disk cache anyway.
 
+fsyncdata=int	Like fsync= but uses fdatasync() to only sync data and not
+		metadata blocks.
+
 overwrite=bool	If true, writes to a file will always overwrite existing
 		data. If the file doesn't already exist, it will be
 		created before the write phase begins. If the file exists
@@ -546,7 +550,9 @@ rwmixread=int	How large a percentage of the mix should be reads.
 rwmixwrite=int	How large a percentage of the mix should be writes. If both
 		rwmixread and rwmixwrite is given and the values do not add
 		up to 100%, the latter of the two will be used to override
-		the first.
+		the first. This may interfere with a given rate setting,
+		if fio is asked to limit reads or writes to a certain rate.
+		If that is the case, then the distribution may be skewed.
 
 norandommap	Normally fio will cover every block of the file when doing
 		random IO. If this option is given, fio will just get a
@@ -925,6 +931,14 @@ gtod_cpu=int	Sometimes it's cheaper to dedicate a single thread of
 		for doing these time calls will be excluded from other
 		uses. Fio will manually clear it from the CPU mask of other
 		jobs.
+continue_on_error=bool	Normally fio will exit the job on the first observed
+		failure. If this option is set, fio will continue the job when
+		there is a 'non-fatal error' (EIO or EILSEQ) until the runtime
+		is exceeded or the I/O size specified is completed. If this
+		option is used, there are two more stats that are appended,
+		the total error count and the first error. The error field
+		given in the stats is the first error that was hit during the
+		run.
 
 
 6.0 Interpreting the output