From 4c09c15f4650107ec89eb0b0c8fc9d90c161dcaf Mon Sep 17 00:00:00 2001 From: Howard Date: Sat, 25 Nov 2017 19:51:43 -1000 Subject: btrfs-progs: docs: update btrfs-subvolume manual page To simplify, I suggest moving the 'writable/readonly' issue only to the -r line, instead of having it introduced in two places. Pull-request: #80 Author: Howard Signed-off-by: David Sterba --- Documentation/btrfs-subvolume.asciidoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/Documentation/btrfs-subvolume.asciidoc b/Documentation/btrfs-subvolume.asciidoc index d33fee5a..c5298cc7 100644 --- a/Documentation/btrfs-subvolume.asciidoc +++ b/Documentation/btrfs-subvolume.asciidoc @@ -154,12 +154,16 @@ The id can be obtained from *btrfs subvolume list*, *btrfs subvolume show* or Show information of a given subvolume in the . *snapshot* [-r] |[/]:: -Create a writable/readonly snapshot of the subvolume with the +Create a snapshot of the subvolume with the name in the directory. + If only is given, the subvolume will be named the basename of . If is not a subvolume, btrfs returns an error. -If '-r' is given, the snapshot will be readonly. ++ +`Options` ++ +-r:::: +Make the new snapshot read only. *sync* [subvolid...]:: Wait until given subvolume(s) are completely removed from the filesystem -- cgit v1.2.3