From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: is back and forth incremental send/receive supported/stable?
Date: Mon, 01 Feb 2021 23:51:06 +0100 [thread overview]
Message-ID: <d73ee44738fc69df8aa3f9a5d3c04c5a88e2731a.camel@scientia.net> (raw)
In-Reply-To: <20210201104609.GO4090@savella.carfax.org.uk>
On Mon, 2021-02-01 at 10:46 +0000, Hugo Mills wrote:
> It'll fail *obviously*. I'm not sure how graceful it is. :)
Okay that doesn't sound like it was very trustworthy... :-/
Especially this from the manpage:
You must not specify clone sources unless you guarantee that these
snapshots are exactly in the same state on both sides—both for the
sender and the receiver.
I mean what should the user ever be able to guarantee... respectively
what's meant with above?
If the tools or any option combination thereof would allow one to
create corrupted send/received shapthots, then there's not much a user
can do.
If this sentence just means that the user mustn't have manually hacked
some UUIDs or so... well then I guess that's anyway clear and the
sentence is just confusing.
> but I guess it's not a priority for the devs
Since it seems to be a valuable feature with probably little chances to
get it working in the foreseeable future, I've added it as a feature
request to the long term records ;-)
https://bugzilla.kernel.org/show_bug.cgi?id=211521
Cheers,
Chris.
next prev parent reply other threads:[~2021-02-01 23:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:09 is back and forth incremental send/receive supported/stable? Christoph Anton Mitterer
2021-01-29 19:18 `
2021-01-29 19:20 ` Hugo Mills
2021-01-31 22:50 ` Christoph Anton Mitterer
2021-02-01 10:46 ` Hugo Mills
2021-02-01 21:53 ` Chris Murphy
2021-02-02 19:42 ` Andrei Borzenkov
2021-02-01 22:51 ` Christoph Anton Mitterer [this message]
2021-02-02 7:53 ` Hugo Mills
2021-02-02 19:44 ` Andrei Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d73ee44738fc69df8aa3f9a5d3c04c5a88e2731a.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox