mirror of https://github.com/mkerrisk/man-pages
open.2, sync_file_range.2, umount.2: Global fix: s/filesystem/file system/
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
d71593a99b
commit
245dec52ca
|
@ -680,7 +680,7 @@ and
|
||||||
.B O_RSYNC
|
.B O_RSYNC
|
||||||
to the same numerical value as
|
to the same numerical value as
|
||||||
.BR O_SYNC
|
.BR O_SYNC
|
||||||
Most Linux filesystems don't actually implement the POSIX
|
Most Linux file systems don't actually implement the POSIX
|
||||||
.B O_SYNC
|
.B O_SYNC
|
||||||
semantics, which require all metadata updates of a write
|
semantics, which require all metadata updates of a write
|
||||||
to be on disk on returning to userspace, but only the
|
to be on disk on returning to userspace, but only the
|
||||||
|
|
|
@ -88,11 +88,11 @@ Therefore, unless the application is strictly performing overwrites of
|
||||||
already-instantiated disk blocks, there are no guarantees that the data will
|
already-instantiated disk blocks, there are no guarantees that the data will
|
||||||
be available after a crash.
|
be available after a crash.
|
||||||
There is no user interface to know if a write is purely an overwrite.
|
There is no user interface to know if a write is purely an overwrite.
|
||||||
On filesystem using copy-on-write semantics (e.g.,
|
On file systems using copy-on-write semantics (e.g.,
|
||||||
.IR btrfs )
|
.IR btrfs )
|
||||||
an overwrite of existing allocated blocks is impossible.
|
an overwrite of existing allocated blocks is impossible.
|
||||||
When writing into preallocated space,
|
When writing into preallocated space,
|
||||||
many filesystems also require calls into the block
|
many file systems also require calls into the block
|
||||||
allocator, which this system call does not sync out to disk.
|
allocator, which this system call does not sync out to disk.
|
||||||
This system call does not flush disk write caches and thus does not provide
|
This system call does not flush disk write caches and thus does not provide
|
||||||
any data integrity on systems with volatile disk write caches.
|
any data integrity on systems with volatile disk write caches.
|
||||||
|
|
|
@ -94,9 +94,9 @@ On error, \-1 is returned, and
|
||||||
.I errno
|
.I errno
|
||||||
is set appropriately.
|
is set appropriately.
|
||||||
.SH ERRORS
|
.SH ERRORS
|
||||||
The error values given below result from filesystem type independent
|
The error values given below result from file-system type independent
|
||||||
errors.
|
errors.
|
||||||
Each filesystem type may have its own special errors and its
|
Each file system type may have its own special errors and its
|
||||||
own special behavior.
|
own special behavior.
|
||||||
See the kernel source code for details.
|
See the kernel source code for details.
|
||||||
.TP
|
.TP
|
||||||
|
|
Loading…
Reference in New Issue