From: Filipe Manana <fdmanana@gmail.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Darrell Enns <darrell@darrellenns.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backup failing with "failed to clone extents" error
Date: Wed, 1 Sep 2021 16:37:07 +0100 [thread overview]
Message-ID: <CAL3q7H7q58ft3sFJ9n_sy8f4NvoXTcrjyghpsgWc34L2iG4MbQ@mail.gmail.com> (raw)
In-Reply-To: <7a858635-2491-cccd-0a29-d1a1d0c9d313@gmail.com>
On Wed, Sep 1, 2021 at 4:34 PM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
>
> On 01.09.2021 17:50, Filipe Manana wrote:
> > On Tue, Aug 31, 2021 at 5:48 PM Darrell Enns <darrell@darrellenns.com> wrote:
> >>
> >> It's btrfs-progs v5.13.1. Debug logs are attached.
> >
> > Ok, now I see what's going on.
> >
> > Somehow you have at least two snapshots (with IDs 881 and 977 on the
> > send filesystem), that have the same 'received_uuid' -
> > e346e5a1-536c-8d42-ba33-c5452dec7888.
> > So these snapshots were received from some other filesystem in the past.
> >
>
> Is there any reason "btrfs receive" does not show actual id of subvolume
> used as clone source in its log messages?
I don't know... No one found it useful before perhaps.
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2021-09-01 15:37 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 [this message]
2021-09-01 17:16 ` Darrell Enns
2021-09-01 17:40 ` Andrei Borzenkov
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=CAL3q7H7q58ft3sFJ9n_sy8f4NvoXTcrjyghpsgWc34L2iG4MbQ@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=arvidjaar@gmail.com \
--cc=darrell@darrellenns.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).