From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: Sage Weil <sage@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: incremental rbd export / sparse files?
Date: Fri, 23 Nov 2012 09:03:59 +0100 [thread overview]
Message-ID: <50AF2DEF.6080109@profihost.ag> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F755782F690@lisa.maurer-it.com>
Am 23.11.2012 07:23, schrieb Dietmar Maurer:
>> 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!
>
> AFAIK, both 'zfs' and 'btrfs' already have such format.
I think zfs could be problematic again with their licenses? If not i
would prefer that one as it is proven and stable.
Greets,
Stefan
next prev parent reply other threads:[~2012-11-23 8: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 [this message]
2012-11-24 0:04 ` Wido den Hollander
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=50AF2DEF.6080109@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dietmar@proxmox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.