From: Darrell Enns <darrell@darrellenns.com>
To: fdmanana@gmail.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Backup failing with "failed to clone extents" error
Date: Mon, 30 Aug 2021 10:37:51 -0700 [thread overview]
Message-ID: <CAOaVUnXXVmGvu-swEkNG-N474BcMAGO1rKvx26RADbQ=OREZUg@mail.gmail.com> (raw)
In-Reply-To: <CAL3q7H46BpkE+aa00Y71SfTizpOo+4ADhBHU2vme4t-aYO6Zuw@mail.gmail.com>
I still have the snapshots, and will try and test with the debug patch
later today. I am actually using -c. I was doing this using snap-sync
(https://github.com/wesbarnett/snap-sync), which uses -c. The full
command for my test is:
btrfs send -vvv -c /.snapshots/327/snapshot
/.snapshots/374/snapshot/|pv|btrfs receive /mnt/backup/test
This is taken directly from what snap-sync does (just with the added
verbosity). Is -c potentially part of the problem?
next prev parent reply other threads:[~2021-08-30 17:38 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 [this message]
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
-- 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='CAOaVUnXXVmGvu-swEkNG-N474BcMAGO1rKvx26RADbQ=OREZUg@mail.gmail.com' \
--to=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).