Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Eric Mesa <eric@ericmesa.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Issues with btrfs send/receive with parents
Date: Tue, 18 Jun 2019 07:15:48 +0300
Message-ID: <52e0b712-2710-b3aa-3247-e2546020050b@gmail.com> (raw)
In-Reply-To: <97541737.v72oTHCfnW@supermario.mushroomkingdom>

[-- Attachment #1.1: Type: text/plain, Size: 1016 bytes --]

14.06.2019 0:22, Eric Mesa пишет:
> 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? 
> 


I do not think there is easy way to fix it for existing subvolumes. So
remove existing ones, and start replication from scratch making sure you
do not have duplicated received_uuid on either source or destination sides.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 23:56 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
2019-06-14  3:55               ` Chris Murphy
2019-07-14 20:59                 ` Eric Mesa
2019-06-18  4:15               ` Andrei Borzenkov [this message]
2019-06-11  3:47   ` Eric Mesa
2019-06-11  1:11 ` Remi Gauvin

Reply instructions:

You may reply publically 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=52e0b712-2710-b3aa-3247-e2546020050b@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=eric@ericmesa.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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox