From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: RAID6 stable enough for production?
Date: Thu, 15 Oct 2015 12:40:36 -0400 [thread overview]
Message-ID: <CAGfcS_mGHBzdevkaj8DHh=2Hkan8CVHmHrTak53UheaBH9pwLA@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtR2-q3NUcDi6bfQUTzChu6wEbozvYEB_eNuK8toMf7KQQ@mail.gmail.com>
On Wed, Oct 14, 2015 at 9:47 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
> For that matter, now that GlusterFS has checksums and snapshots...
Interesting - I haven't kept up with that. Does it actually do
end-to-end checksums? That is, compute the checksum at the time of
storage, store the checksum in the metadata somehow, and ensure the
checksum matches when data is retrieved?
I forget whether it was glusterfs or ceph I was looking at, but some
of those distributed filesystems will only checksum data while in
transit, but not while it is at rest. So, if a server claims it has a
copy of the file, then it is assumed to be a good copy and you never
realize that even though you have 5 copies of that file distributed
around the server you ended up using differs from the other 4.
I'm also not sure if it supports an n+1/2 model like raid5/6, or if it
is just a 2*n model like raid1. If I want to store 5TB of data with
redundancy, I'd prefer to not need 10TB worth of drives to do it,
regardless of how many systems they're spread across.
--
Rich
next prev parent reply other threads:[~2015-10-15 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 20:19 RAID6 stable enough for production? Sjoerd
2015-10-14 20:23 ` Donald Pearson
2015-10-14 20:34 ` Lionel Bouton
2015-10-14 20:53 ` Donald Pearson
2015-10-14 21:15 ` Rich Freeman
2015-10-14 21:19 ` Donald Pearson
2015-10-15 1:47 ` Chris Murphy
2015-10-15 16:40 ` Rich Freeman [this message]
2015-10-15 19:04 ` Chris Murphy
2015-10-14 21:16 ` Lionel Bouton
2015-10-15 1:55 ` Duncan
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='CAGfcS_mGHBzdevkaj8DHh=2Hkan8CVHmHrTak53UheaBH9pwLA@mail.gmail.com' \
--to=r-btrfs@thefreemanclan.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).