From: Jeff Mitchell <jeffrey.mitchell@gmail.com>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: test osd on zfs
Date: Fri, 19 Apr 2013 06:47:24 -0400 [thread overview]
Message-ID: <517120BC.8060205@gmail.com> (raw)
In-Reply-To: <kkpjpj$vs5$1@ger.gmane.org>
Alex Elsayed wrote:
> 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.
Plus (in my real-world experience) *far* better robustness. If Ceph
could use either and both had feature parity, I'd choose ZFS in a
heartbeat. I've had too many simple Btrfs filesystems go corrupt, not
even using any fancy RAID features.
I wasn't aware that Ceph was using btrfs' file-scope clone command. ZFS
doesn't have that, although in theory with the new capabilities system
it could be supported in one implementation without requiring an on-disk
format change.
--Jeff
prev parent reply other threads:[~2013-04-19 10:47 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
2013-04-19 10:47 ` Jeff Mitchell [this message]
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=517120BC.8060205@gmail.com \
--to=jeffrey.mitchell@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=eternaleye@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.