From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unexpected "ERROR: clone: did not find source subvol" on btrfs receive
Date: Tue, 02 Mar 2021 11:00:06 +0100 [thread overview]
Message-ID: <87pn0hooyh.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: <41b096e1-5345-ae9c-810b-685499813183@wetzel-home.de>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
Hallöchen!
Alexander Wetzel writes:
> I have a strange problem with btrfs send/receive. While I can
> create incremental snaphosts but when I try to restore them I
> reproducible get:
>
>> At snapshot 2021-02-20-TEMP
>> ERROR: clone: did not find source subvol
I observe the same thing regularly (but not every time) and logged
it for a couple of weeks, using kernel 5.8.0 (Ubuntu 20.04) for send
and receive, and btrfs-progs v5.4.1. I use send/receive to sync
large VirtualBox images between my two laptops and a server.
I observed:
- UUID and Receive UUID on both sides match the same way, both if
its working or if the error occurs. (I.e., Receive UUID on one
side matches UUID on the other side, which has no Receive UUID.)
- The “Generation” and “Gen at creation” never match, not amongst
each other, and not on sending and receiving side.
- I *seem* to suffer no data loss due to it.
I am willing to log further things, or test things.
Regards,
Torsten.
--
Torsten Bronger
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4913 bytes --]
prev parent reply other threads:[~2021-03-03 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 17:45 Unexpected "ERROR: clone: did not find source subvol" on btrfs receive Alexander Wetzel
2021-02-21 6:54 ` Andrei Borzenkov
2021-02-21 11:16 ` Alexander Wetzel
2021-02-21 11:57 ` Alexander Wetzel
2021-02-21 17:44 ` Alexander Wetzel
2021-03-02 10:00 ` Torsten Bronger [this message]
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=87pn0hooyh.fsf@physik.rwth-aachen.de \
--to=bronger@physik.rwth-aachen.de \
--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