From: Hugo Mills <hugo@carfax.org.uk>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Using send/receive to keep two rootfs-partitions in sync fails with "ERROR: snapshot: cannot find parent subvolume"
Date: Sun, 7 Jan 2024 12:37:46 +0000 [thread overview]
Message-ID: <20240107123746.GF28171@savella.carfax.org.uk> (raw)
In-Reply-To: <CAFvQSYQvUQXabM4XDNH34y=CsbCHmonmwRh_sS=DkxhJWC2oxA@mail.gmail.com>
On Sun, Jan 07, 2024 at 08:06:36AM +0100, Clemens Eisserer wrote:
> Hi,
>
> I would like to use send/receive to keep two root-filesystems in sync,
> as I've been using it for years now for backups where it really does
> wonders (thanks a lot!).
I'm afraid that btrfs incremental send/receive is *only* designed
for one way backups, as you've been using it up to now. It will not
work for bidirectional syncing, and no amount of gymnastics will make
it work. If you want to do bidirectional sync, you'll need to use some
other tool like rsync.
Hugo.
--
Hugo Mills | Anyone using a computer to generate random numbers
hugo@... carfax.org.uk | is, of course, in a state of sin.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Jon von Neumann
next prev parent reply other threads:[~2024-01-07 13:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 7:06 Using send/receive to keep two rootfs-partitions in sync fails with "ERROR: snapshot: cannot find parent subvolume" Clemens Eisserer
2024-01-07 7:19 ` Andrei Borzenkov
2024-01-07 8:10 ` Clemens Eisserer
2024-01-07 8:21 ` Andrei Borzenkov
2024-01-07 8:29 ` Clemens Eisserer
2024-01-07 11:42 ` Clemens Eisserer
2024-01-08 8:21 ` Andrei Borzenkov
2024-01-08 19:36 ` Clemens Eisserer
2024-01-11 18:41 ` Andrei Borzenkov
2024-01-12 8:44 ` Clemens Eisserer
2024-01-13 8:42 ` Andrei Borzenkov
2024-01-07 12:37 ` Hugo Mills [this message]
2024-01-07 20:29 ` Clemens Eisserer
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=20240107123746.GF28171@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=linuxhippy@gmail.com \
/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