From 909131939f750faffb9fab5542c94f14475379f6 Mon Sep 17 00:00:00 2001 From: Filipe David Borba Manana Date: Fri, 23 May 2014 20:14:56 +0100 Subject: 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 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 --- Documentation/btrfs-receive.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'Documentation/btrfs-receive.txt') diff --git a/Documentation/btrfs-receive.txt b/Documentation/btrfs-receive.txt index 82611603..78dc5116 100644 --- a/Documentation/btrfs-receive.txt +++ b/Documentation/btrfs-receive.txt @@ -38,6 +38,9 @@ Use this option to specify a file to use instead. Terminate after receiving an in the data stream. Without this option, the receiver terminates only if an error is recognized or on EOF. +--max-errors :: +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. EXIT STATUS ----------- -- cgit v1.2.3