All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elsayed <eternaleye@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: test osd on zfs
Date: Thu, 18 Apr 2013 13:07:18 -0700	[thread overview]
Message-ID: <kkpjpj$vs5$1@ger.gmane.org> (raw)
In-Reply-To: alpine.DEB.2.00.1304180747200.626@cobra.newdream.net

Sage Weil wrote:

<snip>
> The main things that come to mind:
> 
> - zfs checksumming
> - ceph can eventually use zfs snapshots similarly to how it uses btrfs
>   snapshots to create stable checkpoints as journal reference points,
>   allowing parallel (instead of writeahead) journaling
> - can use raidz beneath a single ceph-osd for better reliability (e.g., 2x
>   * raidz instead of 3x replication)
> 
> ZFS doesn't have a clone function that we can use to enable efficient
> cephfs/rbd/rados snaps, but maybe this will motivate someone to implement
> one. :)

Since Btrfs has implemented raid5/6 support (meaning raidz is only a feature 
gain if you want 3x parity, which is unlikely to be useful for an OSD[1]), 
the checksumming may be the only real benefit since it supports sha256 (in 
addition to the non-cryptographic fletcher2/fletcher4), whereas btrfs only 
has crc32c at this time.

[1] A raidz3 with 4 disks is basically raid1, at which point you may as well 
use Ceph-level replication. And a 5-or-more-disk OSD strikes me as a 
questionable way to set it up, considering Ceph's strengths.


  reply	other threads:[~2013-04-18 20:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <516E7D5C.7080309@nazarianin.com>
2013-04-17 15:19 ` test osd on zfs Sage Weil
2013-04-17 15:57   ` Henry C Chang
2013-04-17 16:37     ` Jeff Mitchell
2013-04-17 17:00       ` Henry C Chang
2013-04-17 17:00       ` Sage Weil
2013-04-17 17:04       ` Yehuda Sadeh
2013-04-17 17:05         ` Sage Weil
2013-04-17 17:15           ` Yehuda Sadeh
2013-04-17 18:06             ` Brian Behlendorf
2013-04-17 18:57             ` Brian Behlendorf
2013-04-17 19:07               ` Yehuda Sadeh
2013-04-17 19:09                 ` Stefan Priebe
2013-04-17 20:16                   ` Mark Nelson
2013-04-17 20:49                     ` Jeff Mitchell
2013-04-17 21:14                     ` Brian Behlendorf
2013-04-18  2:20                       ` Henry C Chang
2013-04-18  5:56                       ` Stefan Priebe - Profihost AG
2013-04-18 14:50                         ` Sage Weil
2013-04-18 20:07                           ` Alex Elsayed [this message]
2013-04-19 10:47                             ` Jeff Mitchell

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='kkpjpj$vs5$1@ger.gmane.org' \
    --to=eternaleye@gmail.com \
    --cc=ceph-devel@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 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.