From: junlion@tormail.org
To: linux-btrfs@vger.kernel.org
Subject: Incremental btrfs receive in opposite direction fails
Date: Fri, 28 Dec 2012 22:42:36 +0000 [thread overview]
Message-ID: <1ToibV-0001fD-SN@internal.tormail.org> (raw)
Hi everyone!
(I use kernel 3.7.1 and mason/btrfs-progs.git head + the receive
lchown patch [1]. Is there a more up to date btrfs-progs repo for
send/receive enthusiasts?)
What I'm trying is basically:
# Transfer a snapshot of my old system from a backup to the new system
btrfs send /mnt/bak/.snap | btrfs receive / # OK
# Merge the old system's files with the new system's files
btrfs subvolume snapshot /.snap /.snap-merge # OK
mkdir /.snap-merge/.old # OK
mv /.snap-merge/* /.snap-merge/.old # OK
cp -a --reflink /* /.snap-merge # OK
btrfs subvolume snapshot -r /.snap-merge /.snap-merge-done # OK
# Incrementally transfer the merged files back to the backup drive
btrfs send -p /.snap /.snap-merge-done | btrfs receive -p /mnt/bak
The last step fails due to the changed direction of the transfer.
"ERROR: could not find parent subvolume". It seems like btrfs receive
cannot find the parent/clone source because it is searching for its UUID
only by looking through the /mnt/bak snapshots' received_uuid fields.
Is there a way for me to directly change the received_uuid of
/mnt/bak/.snap to make it identical to the UUID of /.snap? This looks
like the easiest way if I only need to do it once.
[1] https://patchwork.kernel.org/patch/1606091/
next reply other threads:[~2012-12-28 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 22:42 junlion [this message]
2012-12-29 13:00 ` Incremental btrfs receive in opposite direction fails Alex Lyakas
2012-12-30 6:40 ` junlion
2013-01-02 16:57 ` Jan Schmidt
2013-01-02 20:56 ` Jun Lion
[not found] ` <20130102205351.GA2242@localhost>
2013-01-02 22:19 ` junlion
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=1ToibV-0001fD-SN@internal.tormail.org \
--to=junlion@tormail.org \
--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 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.