From ffd3b4cda25e96a2d44e005696006ff65ba60f41 Mon Sep 17 00:00:00 2001 From: David Sterba Date: Tue, 14 Jul 2020 15:04:05 +0200 Subject: [PATCH] btrfs-progs: docs: note when subvolume cannot be deleted Signed-off-by: David Sterba --- Documentation/btrfs-subvolume.asciidoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/btrfs-subvolume.asciidoc b/Documentation/btrfs-subvolume.asciidoc index 699722af..d3f4aab5 100644 --- a/Documentation/btrfs-subvolume.asciidoc +++ b/Documentation/btrfs-subvolume.asciidoc @@ -78,6 +78,11 @@ 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. + +The default subvolume (see *btrfs subvolume set-default*) cannot be deleted and +returns error (EPERM) and this is logged to the system log. A subvolume that's +currently involved in send (see *btrfs send*) also cannot be deleted until the +send is finished. This is also logged in the system log. ++ `Options` + -c|--commit-after::::