From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [resend] btrfs-send -c fails: reproduction case
Date: Tue, 19 Apr 2016 08:15:30 +0000 (UTC) [thread overview]
Message-ID: <pan$b45bb$cc2503a6$7ae51219$d3903fd2@cox.net> (raw)
In-Reply-To: CAC8+__7sEnSjtpSSG+Wu+J-582bE4guSwP3L3ZUU8N0r-9ATVg@mail.gmail.com
Zachary Vance posted on Sun, 17 Apr 2016 18:46:13 -0700 as excerpted:
> I was already making sure all -c references were both present and
> unmodified, I think the confusion is mostly around whether the parent
> required to use -c, and whether it's an implicit reference volume in
> particular. If it's required, it's impossible to preserve de-duplication
> after deleting the original parent which would be really bad.
AFAIK, send -c does require a parent, but if there's clones and no parent
given, it will try to pick its own from the list of clones given.
Which explains the error complaining about being unable to find a parent,
when given only clone sources that (based on your reproducer) had nothing
in common with the snapshots listed as clones.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2016-04-19 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 21:55 [resend] btrfs-send -c fails: reproduction case Zachary Vance
2016-04-17 22:36 ` Chris Murphy
2016-04-18 1:46 ` Zachary Vance
2016-04-18 20:52 ` Henk Slager
2016-04-19 8:15 ` Duncan [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='pan$b45bb$cc2503a6$7ae51219$d3903fd2@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).