|author||Filipe David Borba Manana <firstname.lastname@example.org>||2014-05-23 20:14:56 +0100|
|committer||David Sterba <email@example.com>||2014-08-22 14:39:32 +0200|
Btrfs-progs: receive, allow to continue after errors happen
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 <firstname.lastname@example.org> Signed-off-by: David Sterba <email@example.com>
Diffstat (limited to 'Documentation/btrfs-receive.txt')
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/btrfs-receive.txt b/Documentation/btrfs-receive.txt
index 82611603..78dc5116 100644
@@ -38,6 +38,9 @@ Use this option to specify a file to use instead.
Terminate after receiving an <end cmd> in the data stream.
Without this option, the receiver terminates only if an error is recognized
or on EOF.
+Terminate as soon as N errors happened while processing commands from the send
+stream. Default value is 1. A value of 0 means no limit.