diff options
Diffstat (limited to 'man2/sync_file_range.2')
| -rw-r--r-- | man2/sync_file_range.2 | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man2/sync_file_range.2 b/man2/sync_file_range.2 index cb0fee13dd..afca9c22b4 100644 --- a/man2/sync_file_range.2 +++ b/man2/sync_file_range.2 @@ -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 be available after a crash. 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 ) an overwrite of existing allocated blocks is impossible. 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. This system call does not flush disk write caches and thus does not provide any data integrity on systems with volatile disk write caches. |