From: Eric Mesa <eric@ericmesa.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Issues with btrfs send/receive with parents
Date: Thu, 13 Jun 2019 17:22:56 -0400 [thread overview]
Message-ID: <97541737.v72oTHCfnW@supermario.mushroomkingdom> (raw)
In-Reply-To: <b2bba48e-a759-cb99-cf2c-04e89bce171e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Thursday, June 13, 2019 2:26:10 AM EDT Andrei Borzenkov wrote:
>
> All your snapshots on source have the same received_uuid (I have no idea
> how is it possible). If received_uuid exists, it is sent to destination
> instead of subvolume UUID to identify matching snapshot. All your backup
> sbapshots on destination also have the same received_uuid which is
> matched against (received_)UUID of source subvolume. In this case
> receive command takes the first found subvolume (probably the most
> recent, i.e. with the smallest generation number). So you send
> differential stream against one subvolume and this stream is applied to
> another subvolume which explains the error.
Yup. Any idea of how to fix?
--
Eric Mesa
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-13 21:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 23:56 Issues with btrfs send/receive with parents Eric Mesa
2019-06-11 1:10 ` Chris Murphy
2019-06-11 3:39 ` Andrei Borzenkov
2019-06-11 4:19 ` Eric Mesa
2019-06-12 5:43 ` Andrei Borzenkov
2019-06-12 23:03 ` Eric Mesa
2019-06-12 23:11 ` Eric Mesa
2019-06-13 6:26 ` Andrei Borzenkov
2019-06-13 21:22 ` Eric Mesa [this message]
2019-06-14 3:55 ` Chris Murphy
2019-07-14 20:59 ` Eric Mesa
2019-06-18 4:15 ` Andrei Borzenkov
2019-06-11 3:47 ` Eric Mesa
2019-06-11 1:11 ` Remi Gauvin
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=97541737.v72oTHCfnW@supermario.mushroomkingdom \
--to=eric@ericmesa.com \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).