diff options
author | David Sterba <dsterba@suse.com> | 2017-07-19 21:01:30 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2017-07-20 17:43:44 +0200 |
commit | 55110d520b19dff386398912b0bfb827fd94fafe (patch) | |
tree | bc989ac13cf3c5f2afcca1ed8030fff6c858d00e /Documentation | |
parent | dbcbcd3bcae89f609e11100e48c2b398d908340c (diff) |
btrfs-progs: docs: adjust wording for subvol delete
Slightly update the text about deletion after the discussion on IRC.
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/btrfs-subvolume.asciidoc | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/Documentation/btrfs-subvolume.asciidoc b/Documentation/btrfs-subvolume.asciidoc index 3419b138..5cfe8856 100644 --- a/Documentation/btrfs-subvolume.asciidoc +++ b/Documentation/btrfs-subvolume.asciidoc @@ -66,10 +66,13 @@ If <subvolume> is not a subvolume, btrfs returns an error but continues if there are more arguments to process. + The corresponding directory is removed instantly but the data blocks are -removed later. The deletion does not involve full commit by default due to -performance reasons (as a consequence, the subvolume may appear again after a -crash). Use one of the '--commit' options to wait until the operation is safely -stored on the media. +removed later in the background. The command returns immediatelly. See `btrfs +subvolume sync` how to wait until the subvolume gets completely removed. ++ +The deletion does not involve full transaction commit by default due to +performance reasons. As a consequence, the subvolume may appear again after a +crash. Use one of the '--commit' options to wait until the operation is +safely stored on the device. + `Options` + |