diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-09-28 18:17:01 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2017-09-28 18:17:01 +0200 |
| commit | c6822f6930a4625ffb968a7fa3216be173402889 (patch) | |
| tree | b18527c4f22a6a620848b0c8afa071cc6f3f2134 /man2/write.2 | |
| parent | 9c93cce7a7076fe727edae46cd923aaa60700572 (diff) | |
| download | man-pages-c6822f6930a4625ffb968a7fa3216be173402889.tar.gz | |
fsync.2, write.2: Minor tweaks to NeilBrown's patch
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man2/write.2')
| -rw-r--r-- | man2/write.2 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man2/write.2 b/man2/write.2 index b1cc3a2cfb..796cae8ba2 100644 --- a/man2/write.2 +++ b/man2/write.2 @@ -181,11 +181,11 @@ or the file offset is not suitably aligned. .TP .B EIO A low-level I/O error occurred while modifying the inode. -This error may relate to the write-back of data written by an -earlier +This error may relate to the write-back of data written by an earlier .BR write (2), which may have been issued to a different file descriptor on -the same file. Since Linux 4.13, errors from write-back come +the same file. +Since Linux 4.13, errors from write-back come with a promise that they .I may be reported by subsequent. @@ -239,11 +239,11 @@ A successful return from .BR write () does not make any guarantee that data has been committed to disk. On some filesystems, including NFS, it does not even guarantee -that space has successfully been reserved for the data. In the case, -some errors might be delayed to a future -.BR write (2) -or to -.BR fsync (2) +that space has successfully been reserved for the data. +In this case, +some errors might be delayed until a future +.BR write (2), +.BR fsync (2), or even .BR close (2). The only way to be sure is to call |