path: root/Documentation/btrfs-receive.txt
Commit message (Collapse)AuthorAge
* Btrfs-progs: receive, allow to continue after errors happenFilipe David Borba Manana2014-08-22
| | | | | | | | | | | | | | | | | | | | Due to either bugs in send (kernel) that generate a command against a wrong path for example, or transient errors on the receiving side, we stopped processing the send stream immediately and exited with an error. It's often desirable to continue processing the send stream even if an error happens while processing a single command from the send stream. This change just adds a --max-errors <N> parameter, whose default value is 1 (preserving current behaviour), that allows to tolerate N errors before stopping. A value of 0 means to never stop no matter how many errors we get into while processing the send stream. Regardless of its value, errors are always printed to stderr when they happen, just like before this change. Signed-off-by: Filipe David Borba Manana <> Signed-off-by: David Sterba <>
* btrfs-progs: doc: update the Availability sectionDavid Sterba2014-05-19
| | | | | | | Does not reflect the current state. The wiki contains more details on the first page. Signed-off-by: David Sterba <>
* btrfs-progs: doc: make all commands and subcommands boldDavid Sterba2014-05-19
| | | | | | | Italic format is used for parameters and values. also this makes the text visually separated, Signed-off-by: David Sterba <>
* btrfs-progs: Convert man page for btrfs-receive.Qu Wenruo2014-04-22
Convert man page for btrfs-receive. Signed-off-by: Qu Wenruo <> Signed-off-by: David Sterba <>