From: Marc MERLIN <marc@merlins.org>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs receive: could not find parent subvolume
Date: Thu, 18 Sep 2014 09:07:01 -0700 [thread overview]
Message-ID: <20140918160701.GO12147@merlins.org> (raw)
In-Reply-To: <20140918153934.GA9830@carfax.org.uk>
On Thu, Sep 18, 2014 at 04:39:34PM +0100, Hugo Mills wrote:
> > 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?
>
> There's a "recieved UUID" field on each subvolume. I posted a patch
> to userspace a couple of weeks ago which adds a -R option to show it.
> I don't think it's filtered through David's backlog yet.
Ah, thanks for that.
Now I wonder why the parent read only snapshot with the same name
on both sides (created by btrfs send) suddenly have a UUID mismatch.
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
prev parent reply other threads:[~2014-09-18 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 15:27 btrfs receive: could not find parent subvolume Marc MERLIN
2014-09-18 15:39 ` Hugo Mills
2014-09-18 16:07 ` Marc MERLIN [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=20140918160701.GO12147@merlins.org \
--to=marc@merlins.org \
--cc=hugo@carfax.org.uk \
--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).