Skip to contentSkip to conversation

btrfs-progs: describe btrfs-send requires read-only subvolume

PATCH Applied Satoru Takeuchi 2 participants 2 messages Feb 4, 2016

Subsystems (2)
Documentation Btrfs file system
lore
Share & tools
lore

Satoru Takeuchi

author
#0 lore raw

PATCH 1/1 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 <[email protected]>
---
 Documentation/btrfs-send.asciidoc | 1 +
 cmds-send.c                       | 1 +
 2 files changed, 2 insertions(+)
Documentation/btrfs-send.asciidoc +1 -0
index 1dba8a3..e05342f 100644
@@ -12,6 +12,7 @@ SYNOPSIS
 DESCRIPTION
 -----------
 Sends the subvolume(s) specified by <subvol> to stdout.
+<subvol> should be read-only here.
 
 By default, this will send the whole subvolume. To do an incremental
 send, use '-p <parent>'.
cmds-send.c +1 -0
index 478ace1..3e34d75 100644
@@ -711,6 +711,7 @@ const char * const cmd_send_usage[] = {
 	"btrfs send [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]",
 	"Send the subvolume(s) to stdout.",
 	"Sends the subvolume(s) specified by <subvol> to stdout.",
+	"<subvol> should be read-only here.",
 	"By default, this will send the whole subvolume. To do an incremental",
 	"send, use '-p <parent>'. If you want to allow btrfs to clone from",
 	"any additional local snapshots, use '-c <clone-src>' (multiple times",
Signature · 1 line
2.5.0