From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Darrell Enns <darrell@darrellenns.com>, fdmanana@gmail.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backup failing with "failed to clone extents" error
Date: Wed, 1 Sep 2021 20:40:50 +0300 [thread overview]
Message-ID: <ce80dccc-f829-5193-a97b-262c669fb29c@gmail.com> (raw)
In-Reply-To: <CAOaVUnW6GzK6ANOUz4x+BBXz90sgaT_TJuQUm869CYa6qH2KSA@mail.gmail.com>
On 01.09.2021 20:16, Darrell Enns wrote:
> I'm not sure how this would happen. These subvolumes were all created
> with snapper (snap-sync just calls snapper). They were not received
> from another filesystem, and I don't think they've ever been RW
> (unless snapper for some reason does that?).
>
> Received_uuid is actually the same on *all* my snapshots, and it's the
> same as the original "@root" subvolume as well. Is each one supposed
> to have a unique received_uuid?
Received_uuid is expected to be managed by "btrfs receive" only. It can
be seen as "dataset identifier" - identical received_uuid means both
subvolumes have identical content (identical from btrfs point of view,
having the same files is not enough). It is valid to cascade
send/receive so if A was sent to B and then B was sent to C, both B and
C will have identical received_uuid equal to A uuid because the have the
same content (all three subvolumes are expected to be read-only and so
cannot be changed).
Unfortunately there are a lot of possibilities to completely break this
workflow. Your case is one example.
> Is this somehow because my "@root"
> subvolume was originally created by receiving from another btrfs?
>
Most likely. Did you simply make received subvolume read-write?
next prev parent reply other threads:[~2021-09-01 17:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 23:22 Backup failing with "failed to clone extents" error Darrell Enns
2021-08-26 9:48 ` Filipe Manana
2021-08-26 18:30 ` Darrell Enns
2021-08-27 11:35 ` Filipe Manana
2021-08-27 18:01 ` Darrell Enns
2021-08-27 19:31 ` Filipe Manana
2021-08-27 21:04 ` Darrell Enns
2021-08-30 10:51 ` Filipe Manana
2021-08-30 16:38 ` Filipe Manana
2021-08-30 17:37 ` Darrell Enns
2021-08-30 18:34 ` Filipe Manana
2021-08-30 19:08 ` Darrell Enns
2021-08-30 19:52 ` Filipe Manana
2021-08-30 20:08 ` Darrell Enns
2021-08-30 20:11 ` Darrell Enns
2021-08-30 20:58 ` Filipe Manana
2021-08-31 2:46 ` Darrell Enns
2021-08-31 11:20 ` Filipe Manana
2021-08-31 11:21 ` Filipe Manana
2021-08-31 16:48 ` Darrell Enns
2021-09-01 14:50 ` Filipe Manana
2021-09-01 15:34 ` Andrei Borzenkov
2021-09-01 15:37 ` Filipe Manana
2021-09-01 17:16 ` Darrell Enns
2021-09-01 17:40 ` Andrei Borzenkov [this message]
2021-09-01 17:52 ` Darrell Enns
2021-09-01 18:16 ` Andrei Borzenkov
2021-09-01 18:28 ` Darrell Enns
-- strict thread matches above, loose matches on Subject: below --
2020-04-16 0:31 Matt Huszagh
2020-04-16 11:53 ` Filipe Manana
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=ce80dccc-f829-5193-a97b-262c669fb29c@gmail.com \
--to=arvidjaar@gmail.com \
--cc=darrell@darrellenns.com \
--cc=fdmanana@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).