From: Harald Hoyer <harald@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Problem with applying incremental btrfs-send
Date: Wed, 03 Sep 2014 14:25:22 +0200 [thread overview]
Message-ID: <540708B2.9090109@redhat.com> (raw)
Hi,
maybe someone can enlighten me. I am doing btrfs send & receive with full
snapshots and incremental updates.
It basically looks like this:
vol-0 and vol-1 are full subvolume image sends.
inc-1 and inc-2 are incremental images with:
# btrfs send -f inc-1 -p vol vol'
# btrfs send -f inc-2 -p vol' vol''
Case A:
vol---send----> vol-0 --receive--> avol --send&rec--> bvol
|-----send----> inc-1 --receive--> | | <--receive-- inc-1
vol' -send----> vol-1 avol' bvol'
|-----send----> inc-2 --receive--> | | <--receive-- inc-2
vol'' avol'' bvol''
which, works for bvol and which even works, if bvol is removed before inc-2 is
applied to bvol'.
Case B:
vol---send----> vol-0 --receive--> avol
|-----send----> inc-1 --receive--> |
vol' -send----> vol-1 avol' --send&rec--> bvol'
|-----send----> inc-2 --receive--> | | <--receive-- inc-2
vol'' avol'' ERROR
trying to apply inc-2 to bvol' fails with:
ERROR: could not find parent subvolume
What's the problem here?
reply other threads:[~2014-09-03 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=540708B2.9090109@redhat.com \
--to=harald@redhat.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).