diff options
author | Dimitri John Ledkov <xnox@ubuntu.com> | 2017-07-31 14:54:24 +0100 |
---|---|---|
committer | Dimitri John Ledkov <xnox@ubuntu.com> | 2017-07-31 14:54:24 +0100 |
commit | 6a0440391da7a99ffab94ccc66264af9b5f3ce34 (patch) | |
tree | 1c7cf4f07b08c4965ab19819ebce367be16fb980 /Documentation/btrfs-send.asciidoc | |
parent | 5f2e2384443a09e3f1fec71940e9e32b70789102 (diff) |
New upstream release.
Diffstat (limited to 'Documentation/btrfs-send.asciidoc')
-rw-r--r-- | Documentation/btrfs-send.asciidoc | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/Documentation/btrfs-send.asciidoc b/Documentation/btrfs-send.asciidoc index 96659eed..ef345f68 100644 --- a/Documentation/btrfs-send.asciidoc +++ b/Documentation/btrfs-send.asciidoc @@ -3,7 +3,7 @@ btrfs-send(8) NAME ---- -btrfs-send - generate a stream of changes between two subvolumes +btrfs-send - generate a stream of changes between two subvolume snapshots SYNOPSIS -------- @@ -13,20 +13,21 @@ DESCRIPTION ----------- This command will generate a stream of instructions that describe changes -between two subvolumes. The stream can be consumed by the *btrfs receive* -command to replicate the sent subvolume on a different filesystem. +between two subvolume snapshots. The stream can be consumed by the *btrfs +receive* command to replicate the sent snapshot on a different filesystem. The command operates in two modes: full and incremental. -All subvolumes involved in one send command must be read-only (ie. the -read-only snapshots and this status cannot be changed if there's a running send -operation that uses the subvolume). +All snapshots involved in one send command must be read-only, and this status +cannot be changed as long as there's a running send operation that uses the +snapshot. -In the full mode, the entire subvolume data and metadata will end up in the +In the full mode, the entire snapshot data and metadata will end up in the stream. -In the incremental mode (options '-p' and '-c'), there can be one or more -parent subvolumes that will establish the base for determining the changes. -The final stream will be smaller compared to the full mode. +In the incremental mode (options '-p' and '-c'), previously sent snapshots that +are available on both the sending and receiving side can be used to reduce the +amount of information that has to be sent to reconstruct the sent snapshot on a +different filesystem. 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 @@ -45,8 +46,8 @@ 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 standard outout so it can be eg. piped to -receive, use this option to write it to a file +output is normally written to standard output so it can be, for example, piped +to btrfs receive. Use this option to write it to a file instead. --no-data:: send in 'NO_FILE_DATA' mode + @@ -58,7 +59,7 @@ useful to show the differences in metadata. enable verbose output, print generated commands in a readable form, (each occurrence of this option increases the verbosity level) -q|--quiet:: -suppress all messagese except errors +suppress all messages except errors EXIT STATUS ----------- |