From: Paul Eggert <eggert@cs.ucla.edu>
Date: Thu, 7 Jul 2022 04:42:19 +0000 (-0500)
Subject: dd: doc improvement (Bug#54586)
X-Git-Tag: v9.2~175
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e6c70916344ea59f64303d6f2e2baec49ff712c6;p=thirdparty%2Fcoreutils.git

dd: doc improvement (Bug#54586)

* doc/coreutils.texi (dd invocation): Explain
fdatasync and fsync better.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 7bca37b71b..e0c87d1ad7 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -9466,7 +9466,13 @@ Continue after read errors.
 @cindex synchronized data writes, before finishing
 Synchronize output data just before finishing,
 even if there were write errors.
-This forces a physical write of output data.
+This forces a physical write of output data,
+so that even if power is lost the output data will be preserved.
+If neither this nor @samp{fsync} are specified, output is treated as
+usual with file systems, i.e., output data and metadata may be cached
+in primary memory for some time before the operating system physically
+writes it, and thus output data and metadata may be lost if power is lost.
+@xref{sync invocation}.
 This conversion is a GNU extension to POSIX.
 
 @item fsync
@@ -9474,7 +9480,10 @@ This conversion is a GNU extension to POSIX.
 @cindex synchronized data and metadata writes, before finishing
 Synchronize output data and metadata just before finishing,
 even if there were write errors.
-This forces a physical write of output data and metadata.
+This acts like @samp{fdatasync} except it also preserves output metadata,
+such as the last-modified time of the output file; for this reason it
+may be a bit slower than @samp{fdatasync} although the performance
+difference is typically insignificant for @command{dd}.
 This conversion is a GNU extension to POSIX.
 
 @end table