1BTRFS-SEND(8) BTRFS BTRFS-SEND(8)
2
3
4
6 btrfs-send - generate a stream of changes between two subvolume snap‐
7 shots
8
10 btrfs send [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol>
11 [<subvol>...]
12
14 This command will generate a stream of instructions that describe
15 changes between two subvolume snapshots. The stream can be consumed by
16 the btrfs receive command to replicate the sent snapshot on a different
17 filesystem. The command operates in two modes: full and incremental.
18
19 All snapshots involved in one send command must be read-only, and this
20 status cannot be changed as long as there's a running send operation
21 that uses the snapshot.
22
23 In the full mode, the entire snapshot data and metadata will end up in
24 the stream.
25
26 In the incremental mode (options -p and -c), previously sent snapshots
27 that are available on both the sending and receiving side can be used
28 to reduce the amount of information that has to be sent to reconstruct
29 the sent snapshot on a different filesystem.
30
31 The -p <parent> option can be omitted when -c <clone-src> options are
32 given, in which case btrfs send will determine a suitable parent from
33 among the clone sources.
34
35 You must not specify clone sources unless you guarantee that these
36 snapshots are exactly in the same state on both sides--both for the
37 sender and the receiver. For implications of changed read-write status
38 of a received snapshot please see section SUBVOLUME FLAGS in btrfs-sub‐
39 volume(8).
40
41 Options
42
43 -e if sending multiple subvolumes at once, use the new format and
44 omit the 'end cmd' marker in the stream separating the subvol‐
45 umes
46
47 -p <parent>
48 send an incremental stream from parent to subvol
49
50 -c <clone-src>
51 use this snapshot as a clone source for an incremental send
52 (multiple allowed)
53
54 -f <outfile>
55 output is normally written to standard output so it can be, for
56 example, piped to btrfs receive. Use this option to write it to
57 a file instead.
58
59 --no-data::
60 send in NO_FILE_DATA mode
61
62 The output stream does not contain any file data and thus cannot
63 be used to transfer changes. This mode is faster and is useful
64 to show the differences in metadata.
65
66 -q|--quiet
67 (deprecated) alias for global -q option
68
69 -v|--verbose
70 (deprecated) alias for global -v option
71
72 Global options
73
74 -q|--quiet
75 suppress all messages except errors
76
77 -v|--verbose
78 increase output verbosity, print generated commands in a read‐
79 able form
80
82 btrfs send returns a zero exit status if it succeeds. Non zero is re‐
83 turned in case of failure.
84
86 btrfs is part of btrfs-progs. Please refer to the btrfs wiki
87 http://btrfs.wiki.kernel.org for further details.
88
90 mkfs.btrfs(8), btrfs-receive(8), btrfs-subvolume(8)
91
93 2022
94
95
96
97
985.18 May 25, 2022 BTRFS-SEND(8)