From dbd11ead507f28becae47919f0c5cf03a7fef58d Mon Sep 17 00:00:00 2001 From: Jens Axboe Date: Sun, 13 Jan 2013 17:16:46 +0100 Subject: [PATCH] Improve documentation for end_fsync Signed-off-by: Jens Axboe --- HOWTO | 2 +- fio.1 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/HOWTO b/HOWTO index 014b7f3d..d5be376d 100644 --- a/HOWTO +++ b/HOWTO @@ -704,7 +704,7 @@ overwrite=bool If true, writes to a file will always overwrite existing and is large enough for the specified write phase, nothing will be done. -end_fsync=bool If true, fsync file contents when the job exits. +end_fsync=bool If true, fsync file contents when a write stage has completed. fsync_on_close=bool If true, fio will fsync() a dirty file on close. This differs from end_fsync in that it will happen on every diff --git a/fio.1 b/fio.1 index 5b65e078..2f7728ab 100644 --- a/fio.1 +++ b/fio.1 @@ -561,7 +561,7 @@ Also see the sync_file_range(2) man page. This option is Linux specific. If writing, setup the file first and do overwrites. Default: false. .TP .BI end_fsync \fR=\fPbool -Sync file contents when job exits. Default: false. +Sync file contents when a write stage has completed. Default: false. .TP .BI fsync_on_close \fR=\fPbool If true, sync file contents on close. This differs from \fBend_fsync\fR in that -- 2.25.1