From 194a4053f97b9897a470938c3fb68e2b92e323f2 Mon Sep 17 00:00:00 2001 From: Satoru Takeuchi Date: Thu, 4 Feb 2016 14:02:14 +0900 Subject: [PATCH] btrfs-progs: describe btrfs-send requires read-only subvolume Both man btrfs-send(8) and usage message don't describe btrfs-send needs read-only snapshot as its argument. Signed-off-by: Satoru Takeuchi Signed-off-by: David Sterba --- Documentation/btrfs-send.asciidoc | 1 + cmds-send.c | 1 + 2 files changed, 2 insertions(+) diff --git a/Documentation/btrfs-send.asciidoc b/Documentation/btrfs-send.asciidoc index 1dba8a3d..e05342ff 100644 --- a/Documentation/btrfs-send.asciidoc +++ b/Documentation/btrfs-send.asciidoc @@ -12,6 +12,7 @@ SYNOPSIS DESCRIPTION ----------- Sends the subvolume(s) specified by to stdout. + should be read-only here. By default, this will send the whole subvolume. To do an incremental send, use '-p '. diff --git a/cmds-send.c b/cmds-send.c index 478ace1f..3e34d75b 100644 --- a/cmds-send.c +++ b/cmds-send.c @@ -711,6 +711,7 @@ const char * const cmd_send_usage[] = { "btrfs send [-ve] [-p ] [-c ] [-f ] [...]", "Send the subvolume(s) to stdout.", "Sends the subvolume(s) specified by to stdout.", + " should be read-only here.", "By default, this will send the whole subvolume. To do an incremental", "send, use '-p '. If you want to allow btrfs to clone from", "any additional local snapshots, use '-c ' (multiple times",