Update comments about availability of fdatasync().

FreeBSD 11 added fdatasync(2), in 2016.

Signed-off-by: Thomas Munro <thomas.munro@gmail.com>

diff --git a/HOWTO b/HOWTO
index 8c9e41356b9586b33fa17e4068d50620eb6be551..901305aad5b644c219f4e9efd9cfef946ead8006 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -1338,7 +1338,7 @@ I/O type
 .. option:: fdatasync=int
 
        Like :option:`fsync` but uses :manpage:`fdatasync(2)` to only sync data and
-       not metadata blocks. In Windows, FreeBSD, DragonFlyBSD or OSX there is no
+       not metadata blocks. In Windows, DragonFlyBSD or OSX there is no
        :manpage:`fdatasync(2)` so this falls back to using :manpage:`fsync(2)`.
        Defaults to 0, which means fio does not periodically issue and wait for a
        data-only sync to complete.

diff --git a/fio.1 b/fio.1
index a3ebb67d36df6884ea1ce95ca5cfb48946bec0a6..379225289afa8684b6f1c7364c8cac5d19418516 100644 (file)
--- a/fio.1
+++ b/fio.1
@@ -1122,7 +1122,7 @@ see \fBend_fsync\fR and \fBfsync_on_close\fR.
 .TP
 .BI fdatasync \fR=\fPint
 Like \fBfsync\fR but uses \fBfdatasync\fR\|(2) to only sync data and
-not metadata blocks. In Windows, FreeBSD, DragonFlyBSD or OSX there is no
+not metadata blocks. In Windows, DragonFlyBSD or OSX there is no
 \fBfdatasync\fR\|(2) so this falls back to using \fBfsync\fR\|(2).
 Defaults to 0, which means fio does not periodically issue and wait for a
 data-only sync to complete.