From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs receive: could not find parent subvolume
Date: Thu, 18 Sep 2014 08:27:18 -0700 [thread overview]
Message-ID: <20140918152718.GA27983@merlins.org> (raw)
While debugging a btrfs send/receive slow problem, I now getting this:
legolas:/mnt/btrfs_pool1# btrfs send -p tmp_ggm_daily_ro.20140917_06:29:58 tmp_ggm_daily_ro.20140918_02:48:24 | ssh gargamel btrfs receive -v /mnt/btrfs_pool2/backup/debian64/legolas
At subvol tmp_ggm_daily_ro.20140918_02:48:24
At snapshot tmp_ggm_daily_ro.20140918_02:48:24
receiving snapshot tmp_ggm_daily_ro.20140918_02:48:24 uuid=5d1f0454-1be3-b648-9ea5-dc427cd62d98, ctransid=310713 parent_uuid=d86e69bf-e17f-7f4c-bfb7-e571d5824687, parent_ctransid=308332
ERROR: could not find parent subvolume
The parent is there on the other side, but UUID is different:
gargamel:/mnt/btrfs_pool2/backup/debian64/legolas# btrfs subvolume show tmp_ggm_daily_ro.20140917_06:29:58
/mnt/btrfs_pool2/backup/debian64/legolas/tmp_ggm_daily_ro.20140917_06:29:58
Name: tmp_ggm_daily_ro.20140917_06:29:58
uuid: 3d424a2b-69da-244c-bfcc-c283f9cc1f34
Parent uuid: 05d3b9be-bfe2-bb4a-9f6a-64b9d44896c7
Creation time: 2014-09-17 06:30:01
Object ID: 7873
Generation (Gen): 83621
Gen at creation: 83476
Parent: 263
Top Level: 263
Flags: -
Snapshot(s):
Now it seems that the UUID is different on all my snapshots created by
btrfs send, so maybe it doesn't match UUID?
Given that, what is btrfs receive using to get a match?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
next reply other threads:[~2014-09-18 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:27 Marc MERLIN [this message]
2014-09-18 15:39 ` btrfs receive: could not find parent subvolume Hugo Mills
2014-09-18 16:07 ` Marc MERLIN
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=20140918152718.GA27983@merlins.org \
--to=marc@merlins.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 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).