diff options
author | David Sterba <dsterba@suse.com> | 2016-09-06 19:06:42 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2016-09-21 11:47:38 +0200 |
commit | 67786272eaed79f3803847f6bca573cea4be16a9 (patch) | |
tree | 3042e3d64f4a710b5544141fbc8e08af51d56793 /Documentation | |
parent | f04db96f617cf02d4020c4befe7558d1e3cc22c4 (diff) |
btrfs-progs: docs: update flushoncommit default value
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/btrfs-man5.asciidoc | 15 |
1 files changed, 9 insertions, 6 deletions
diff --git a/Documentation/btrfs-man5.asciidoc b/Documentation/btrfs-man5.asciidoc index a1f364e0..caa9390b 100644 --- a/Documentation/btrfs-man5.asciidoc +++ b/Documentation/btrfs-man5.asciidoc @@ -214,15 +214,18 @@ parameters, eg. 'panic', 'oops' or 'crashkernel'. *flushoncommit*:: *noflushoncommit*:: -(default: on) +(default: off) + This option forces any data dirtied by a write in a prior transaction to commit -as part of the current commit. This makes the committed state a fully -consistent view of the file system from the application's perspective (i.e., it -includes all completed file system operations). This was previously the -behavior only when a snapshot was created. +as part of the current commit, effectively a full filesystem sync. ++ +This makes the committed state a fully consistent view of the file system from +the application's perspective (i.e., it includes all completed file system +operations). This was previously the behavior only when a snapshot was +created. + -Disabling flushing may improve performance but is not crash-safe. +When off, the filesystem is consistent but buffered writes may last more than +one transaction commit. *fragment='type'*:: (depends on compile-time option BTRFS_DEBUG, since: 4.4, default: off) |