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: Sun, 31 Jan 2021 23:50:22 +0100 [thread overview]
Message-ID: <956e08b1aed7805f7ee387cc4994702c02b61560.camel@scientia.net> (raw)
In-Reply-To: <20210129192058.GN4090@savella.carfax.org.uk>
Hey Hugo.
Thanks for your explanation.
I assume such a swapped send/receive would fail at least gracefully?
On Fri, 2021-01-29 at 19:20 +0000, Hugo Mills wrote:
> In your scenario with MASTER and COPY-1 swapped, you'd have to
> match the received_uuid from the sending side (on old COPY-1) to the
> actual UUID on old MASTER. The code doesn't do this, so you'd have to
> patch send/receive to do this.
Well from the mailing list thread you've referenced it seems that the
whole thing is rather quite non-trivial... so I guess it's nothing for
someone who has basically no insight into btrfs code ^^
It's a pity though, that this doesn't work. Especially the use case of
sending back (backup)snapshots would seem pretty useful.
Given that this thread is nearly 6 years, I'd guess the whole idea has
been abandoned upstream?!
Cheers,
Chris.
next prev parent reply other threads:[~2021-01-31 23:00 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 [this message]
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
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=956e08b1aed7805f7ee387cc4994702c02b61560.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