{ "content": [ { "type": "text", "text": "# BTRFS-SEND (man)\n\n## NAME\n\nbtrfs-send - generate a stream of changes between two subvolume snapshots\n\n## SYNOPSIS\n\nbtrfs send [-ve] [-p ] [-c ] [-f ] [...]\n\n## DESCRIPTION\n\nThis command will generate a stream of instructions that describe changes between two\nsubvolume snapshots. The stream can be consumed by the btrfs receive command to replicate the\nsent snapshot on a different filesystem. The command operates in two modes: full and\nincremental.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION** (4 subsections)\n- **EXIT STATUS**\n- **AVAILABILITY**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "BTRFS-SEND", "section": "", "mode": "man", "summary": "btrfs-send - generate a stream of changes between two subvolume snapshots", "synopsis": "btrfs send [-ve] [-p ] [-c ] [-f ] [...]", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [ { "flag": "-e", "long": null, "arg": null, "description": "if sending multiple subvolumes at once, use the new format and omit the end cmd marker in the stream separating the subvolumes -p send an incremental stream from parent to subvol -c use this snapshot as a clone source for an incremental send (multiple allowed) -f 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." }, { "flag": "", "long": "--no-data", "arg": null, "description": "send in NOFILEDATA mode The output stream does not contain any file data and thus cannot be used to transfer changes. This mode is faster and is useful to show the differences in metadata. -q|--quiet:::: (deprecated) alias for global -q option -v|--verbose:: (deprecated) alias for global -v option" } ], "examples": [], "see_also": [ { "name": "mkfs.btrfs", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/mkfs.btrfs/8/json" }, { "name": "btrfs-receive", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/btrfs-receive/8/json" }, { "name": "btrfs-subvolume", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/btrfs-subvolume/8/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 22, "subsections": [ { "name": "Options", "lines": 1 }, { "name": "-e", "lines": 13, "flag": "-e" }, { "name": "--no-data", "lines": 7, "long": "--no-data" }, { "name": "Global options", "lines": 6 } ] }, { "name": "EXIT STATUS", "lines": 3, "subsections": [] }, { "name": "AVAILABILITY", "lines": 3, "subsections": [] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] } ], "sections": { "NAME": { "content": "btrfs-send - generate a stream of changes between two subvolume snapshots\n", "subsections": [] }, "SYNOPSIS": { "content": "btrfs send [-ve] [-p ] [-c ] [-f ] [...]\n", "subsections": [] }, "DESCRIPTION": { "content": "This command will generate a stream of instructions that describe changes between two\nsubvolume snapshots. The stream can be consumed by the btrfs receive command to replicate the\nsent snapshot on a different filesystem. The command operates in two modes: full and\nincremental.\n\nAll snapshots involved in one send command must be read-only, and this status cannot be\nchanged as long as there’s a running send operation that uses the snapshot.\n\nIn the full mode, the entire snapshot data and metadata will end up in the stream.\n\nIn the incremental mode (options -p and -c), previously sent snapshots that are available on\nboth the sending and receiving side can be used to reduce the amount of information that has\nto be sent to reconstruct the sent snapshot on a different filesystem.\n\nThe -p option can be omitted when -c options are given, in which case\nbtrfs send will determine a suitable parent from among the clone sources.\n\nYou must not specify clone sources unless you guarantee that these snapshots are exactly in\nthe same state on both sides—both for the sender and the receiver. For implications of\nchanged read-write status of a received snapshot please see section SUBVOLUME FLAGS in\nbtrfs-subvolume(8).\n", "subsections": [ { "name": "Options", "content": "" }, { "name": "-e", "content": "if sending multiple subvolumes at once, use the new format and omit the end cmd marker in\nthe stream separating the subvolumes\n\n-p \nsend an incremental stream from parent to subvol\n\n-c \nuse this snapshot as a clone source for an incremental send (multiple allowed)\n\n-f \noutput is normally written to standard output so it can be, for example, piped to btrfs\nreceive. Use this option to write it to a file instead.\n", "flag": "-e" }, { "name": "--no-data", "content": "send in NOFILEDATA mode\n\nThe output stream does not contain any file data and thus cannot be used to transfer\nchanges. This mode is faster and is useful to show the differences in metadata.\n-q|--quiet:::: (deprecated) alias for global -q option -v|--verbose:: (deprecated) alias\nfor global -v option\n", "long": "--no-data" }, { "name": "Global options", "content": "-q|--quiet\nsuppress all messages except errors\n\n-v|--verbose\nincrease output verbosity, print generated commands in a readable form\n" } ] }, "EXIT STATUS": { "content": "btrfs send returns a zero exit status if it succeeds. Non zero is returned in case of\nfailure.\n", "subsections": [] }, "AVAILABILITY": { "content": "btrfs is part of btrfs-progs. Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for\nfurther details.\n", "subsections": [] }, "SEE ALSO": { "content": "mkfs.btrfs(8), btrfs-receive(8), btrfs-subvolume(8)\n\n\n\nBtrfs v5.16.2 02/16/2022 BTRFS-SEND(8)", "subsections": [] } } } }