From: David Disseldorp <ddiss@suse.de>
To: Sage Weil <sage@inktank.com>
Cc: Ugis <ugis22@gmail.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@ceph.com" <ceph-users@ceph.com>
Subject: Re: ocfs2 for OSDs?
Date: Wed, 11 Sep 2013 21:55:11 +0200 [thread overview]
Message-ID: <20130911215511.3ae4e85a@plati.site> (raw)
In-Reply-To: <alpine.DEB.2.00.1309110916180.23522@cobra.newdream.net>
Hi Sage,
On Wed, 11 Sep 2013 09:18:13 -0700 (PDT)
Sage Weil <sage@inktank.com> wrote:
> > REFLINKs (inode-based writeable snapshots)
>
> This is the one item on this list I see that the ceph-osds could take real
> advantage of; it would make object clones triggered by things like RBD
> snapshots faster. What is missing from this list that would be similarly
> (or more) useful is a volume/fs snapshot feature.
I must be missing something here, but I don't see how this would offer
any advantage over Btrfs, which provides the same feature via
BTRFS_IOC_CLONE and BTRFS_IOC_CLONE_RANGE.
Cheers, David
next prev parent reply other threads:[~2013-09-11 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 13:58 ocfs2 for OSDs? Ugis
[not found] ` <CAE63xUNKj7JnU_Kypnh39j4z6qVPh2ZLCdiEvfis3_9fDBZ2FA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-11 16:18 ` Sage Weil
2013-09-11 19:55 ` David Disseldorp [this message]
2013-09-11 20:02 ` Gregory Farnum
2013-09-12 15:13 ` Jeff Bachtel
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=20130911215511.3ae4e85a@plati.site \
--to=ddiss@suse.de \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@ceph.com \
--cc=sage@inktank.com \
--cc=ugis22@gmail.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.