From: Wido den Hollander <wido@widodh.nl>
To: Sage Weil <sage@inktank.com>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: incremental rbd export / sparse files?
Date: Sat, 24 Nov 2012 08:04:27 +0800 [thread overview]
Message-ID: <50B00F0B.2020807@widodh.nl> (raw)
In-Reply-To: <alpine.DEB.2.00.1211221357480.9963@cobra.newdream.net>
On 11/23/2012 05:59 AM, Sage Weil wrote:
> On Thu, 22 Nov 2012, Stefan Priebe - Profihost AG wrote:
>> Hello list,
>>
>> right now a rbd export exports exactly the size of the disk even if there is
>> KNOWN free space. Is this inteded to change?
>>
>> Might it be possible to export just differences between snapshots and merge
>> them later?
>
> We were just talking about this the other day.
>
> Step 1 is to create a mechanism to output a list of block ranges that
> have/have not changed between snapshots.
>
> Step 2 is to export the incremental changes. The hangup there is figuring
> out a generic and portable file format to represent those incremental
> changes; we'd rather not invent something ourselves that is ceph-specific.
> Suggestions welcome!
>
I'm not sure about the licensing and such, but doesn't VMware do
something with their VMDK images?
There you have a base image and each snapshot is a separate file.
You have:
image.vmdk
image-delta1.vmdk
image-delta2.vmdk
..
..
You can merge all these files together again to a new image based on the
last snapshot you feeded it.
They probably didn't use a open format to do this, but something in that
direction is what you are looking for?
Wido
> sage
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-24 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 11:02 incremental rbd export / sparse files? Stefan Priebe - Profihost AG
2012-11-22 21:59 ` Sage Weil
2012-11-23 6:23 ` Dietmar Maurer
2012-11-23 8:03 ` Stefan Priebe - Profihost AG
2012-11-24 0:04 ` Wido den Hollander [this message]
2012-11-24 6:31 ` Stefan Priebe - Profihost AG
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=50B00F0B.2020807@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=sage@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