linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darrell Enns <darrell@darrellenns.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: fdmanana@gmail.com, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backup failing with "failed to clone extents" error
Date: Wed, 1 Sep 2021 11:28:54 -0700	[thread overview]
Message-ID: <CAOaVUnUvKu7QC=nRUzj-nMYxEiUy7xcHx=e3J6vJsaQ_AkVzmw@mail.gmail.com> (raw)
In-Reply-To: <06e92a0b-e71b-eb21-edb5-9d2a5513b718@gmail.com>

> There was proposed patch to clear received_uuid on
> clearing read-only subvolume property, but it has never been applied.

Exactly this was about to be my next suggestion. I don't know all the
details, but it sounds like that makes sense if matching
received_uuid's is considered to mean the data is identical.

> What will surely work is cloning you root subvolume and switching to
> clone. If course you will need to restart all replication streams
> beginning with full send of new root. But as it looks like you will need
> to restart it anyway.

I will give this a try. Thank you very much for all your help diagnosing this!

  reply	other threads:[~2021-09-01 18:29 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
2021-09-01 17:52                                           ` Darrell Enns
2021-09-01 18:16                                             ` Andrei Borzenkov
2021-09-01 18:28                                               ` Darrell Enns [this message]
  -- 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='CAOaVUnUvKu7QC=nRUzj-nMYxEiUy7xcHx=e3J6vJsaQ_AkVzmw@mail.gmail.com' \
    --to=darrell@darrellenns.com \
    --cc=arvidjaar@gmail.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).