From: Dan Mick <dan.mick@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Josh Durgin <josh.durgin@inktank.com>,
Tommi Virtanen <tv@inktank.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: RBD layering design draft
Date: Mon, 18 Jun 2012 16:07:16 -0700 [thread overview]
Message-ID: <4FDFB4A4.1080107@inktank.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206181059040.11790@cobra.newdream.net>
On 06/18/2012 11:01 AM, Sage Weil wrote:
> On Mon, 18 Jun 2012, Josh Durgin wrote:
>>>> $ rbd copyup pool2/child1
>>>
>>> Does "copyup" make sense to everyone? Every time you say it, my brain
>>> needs to flip the image inside the other way around -- I naturally
>>> imagine a tree with the parent at the top, and children and
>>> grandchildren down from it, but then I can't call that operation
>>> "copyup" without wrecking my mental image.
>>>
>>> I also can't seem to google good evidence that the term would be in
>>> widespread use in the enterprisey block storage world, outside of the
>>> unionfs world.. What do people call the un-dedupping, un-thinning of
>>> copy-on-write thin provisioning?
>>>
>>> "unshare"?
>>
>> I'm not sure what best term is, but there's probably something better than
>> copyup.
>
> "flatten"? My mental model is stuck on the "layering" analogy, where the
> child is a copy-on-write layer on top of a read-only parent.
>
> Someday we may want to support the ability to add a parent to an existing
> image and do a sort of "dedup", so having an opposite for whatever term we
> pick would be a bonus.
"disown" and "adopt"? :) (actually I started as a joke, but really I
kinda like that; fits with the parent-child name)
next prev parent reply other threads:[~2012-06-18 23:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 20:48 RBD layering design draft Josh Durgin
2012-06-16 0:46 ` Sage Weil
2012-06-16 2:00 ` Yehuda Sadeh
2012-06-16 15:11 ` Sage Weil
2012-06-17 13:42 ` Martin Mailand
2012-06-18 18:04 ` Gregory Farnum
2012-06-18 16:25 ` Tommi Virtanen
2012-06-18 23:10 ` Dan Mick
2012-06-18 17:00 ` Tommi Virtanen
2012-06-18 17:14 ` Josh Durgin
2012-06-18 18:01 ` Sage Weil
2012-06-18 23:07 ` Dan Mick [this message]
2012-06-22 2:02 ` Alex Elsayed
2012-06-22 14:41 ` Guido Winkelmann
2012-06-22 14:36 ` Guido Winkelmann
2012-06-22 16:00 ` Tommi Virtanen
2012-06-21 21:51 ` Alex Elder
2012-06-22 14:37 ` Guido Winkelmann
2012-06-22 16:27 ` Tommi Virtanen
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=4FDFB4A4.1080107@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=sage@inktank.com \
--cc=tv@inktank.com \
/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