path: root/Documentation/btrfs-send.txt
diff options
authorQu Wenruo <>2014-04-02 16:29:21 +0800
committerDavid Sterba <>2014-04-22 14:15:21 +0200
commit1873426ece07b0b05155a47e70c47f99a2ad81ab (patch)
tree5d6e6150f5a519d42f3d1a098bfa0808338c5d34 /Documentation/btrfs-send.txt
parent17abe51d4e7a3c89d6bb22af18ba916c3e7cf9ee (diff)
btrfs-progs: Convert man page for btrfs-send.
Convert man page for btrfs-send. Signed-off-by: Qu Wenruo <> Signed-off-by: David Sterba <>
Diffstat (limited to 'Documentation/btrfs-send.txt')
1 files changed, 60 insertions, 0 deletions
diff --git a/Documentation/btrfs-send.txt b/Documentation/btrfs-send.txt
new file mode 100644
index 00000000..18a98fa3
--- /dev/null
+++ b/Documentation/btrfs-send.txt
@@ -0,0 +1,60 @@
+btrfs-send - send data of subvolume(s) to stdout/file.
+'btrfs send' [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]
+Sends the subvolume(s) specified by <subvol> to stdout.
+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 where applicable).
+You must not specify clone sources unless you guarantee that these snapshots
+are exactly in the same state on both sides, the sender and the receiver.
+It is allowed to omit the '-p <parent>' option when '-c <clone-src>' options
+are given, in which case 'btrfs send' will determine a suitable parent among the
+clone sources itself.
+Enable verbose debug output. Each occurrence of this option increases the
+verbose level more.
+If sending multiple subvols at once, use the new format and omit the <end cmd> between the subvols.
+-p <parent>::
+Send an incremental stream from <parent> to <subvol>.
+-c <clone-src>::
+Use this snapshot as a clone source for an incremental send (multiple allowed).
+-f <outfile>::
+Output is normally written to stdout. To write to a file, use this option.
+An alternative would be to use pipes.
+'btrfs send' returns a zero exist status if it succeeds. Non zero is
+returned in case of failure.
+'btrfs' is part of btrfs-progs. Btrfs filesystem is currently under heavy
+and not suitable for any uses other than benchmarking and review.
+Please refer to the btrfs wiki for
+further details.