From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: "list, btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send /receive : having problems sending a snapshot back to the original partition
Date: Wed, 03 Jul 2013 11:11:56 +0100 [thread overview]
Message-ID: <51D3F8EC.4030805@friendlyvirus.org> (raw)
In-Reply-To: <51D2C1FD.5030405@giantdisaster.de>
Em 02-07-2013 13:05, Stefan Behrens escreveu:
> The reason why you are not able to send an incremental snapshot back
> (as you tried it in your previous mail) is that the implementation
> cannot handle it. The receive side gets a parent_uuid (in case of
> incremental transfers using the "-p" option), this parent_uuid is
> matched to the fields received_uuid of the subvolumes in the receive
> filesystem. If no match is found, the receive fails. And that is what
> happens.
>
> If you look at the following script, you can see the expected
> parent_uuid in the line before the "ERROR: could not find parent
> subvolume". And when you look at the output of "btrfs subv list ...
> /mnt/a", you notice that no subvolume at all has the field ruuid
> (which stands for received_uuid) set to any valid value. Therefore it
> doesn't match, therefore it fails.
>
> This logic could be changed, but that's how it is today.
Hi Stefan,
Thank you for the detailed explanation, I guess I understand it better
now. I guess for the time being I have to use rsync to get the data back
or transfer the whole subvolume back.
thanks,
--
Miguel Negrão
http://www.friendlyvirus.org/miguelnegrao
prev parent reply other threads:[~2013-07-03 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 17:14 btrfs send /receive : having problems sending a snapshot back to the original partition Miguel Negrão
2013-07-01 15:50 ` Stefan Behrens
2013-07-02 9:56 ` Miguel Negrão
2013-07-02 12:05 ` Stefan Behrens
2013-07-03 10:11 ` Miguel Negrão [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=51D3F8EC.4030805@friendlyvirus.org \
--to=miguel.negrao-lists@friendlyvirus.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.