From: Roman Mamedov <rm@romanrm.ru>
To: Matt Garman <matthew.garman@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm vs zfs for home server?
Date: Tue, 28 May 2013 01:20:13 +0600 [thread overview]
Message-ID: <20130528012013.2d428584@natsu> (raw)
In-Reply-To: <20130527180912.GA6068@septictank.raw-sewage.fake>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Mon, 27 May 2013 13:09:12 -0500
Matt Garman <matthew.garman@gmail.com> wrote:
> the way to go. I don't know how necessary it is, but I like the
> idea of having the in-filesystem checksums to prevent "silent" data
> corruption.
On some machines I run btrfs on top of MD RAID. In this configuration btrfs
can't heal checksum errors, but will still detect them if they appear.
btrfs now also has built-in RAID5 and RAID6 which *can* heal errors, but
that's still way too immature for being actually used. In fact one may
consider btrfs as a whole to be not mature enough yet, but in my experience
without using fancy cutting edge features like RAID it generally works, and I
don't remember seeing mailing list reports of any data loss or corruption from
anyone in a long time.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-05-27 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 18:09 mdadm vs zfs for home server? Matt Garman
2013-05-27 19:02 ` Roy Sigurd Karlsbakk
2013-05-28 15:00 ` Matt Garman
2013-05-28 15:18 ` Jon Nelson
2013-05-27 19:20 ` Roman Mamedov [this message]
2013-05-27 22:33 ` Stan Hoeppner
2013-05-27 23:50 ` Phil Turmel
2013-05-28 5:12 ` Stan Hoeppner
2013-05-28 15:24 ` Matt Garman
2013-05-28 15:55 ` Ryan Wagoner
-- strict thread matches above, loose matches on Subject: below --
2013-05-28 3:09 Ryan Wagoner
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=20130528012013.2d428584@natsu \
--to=rm@romanrm.ru \
--cc=linux-raid@vger.kernel.org \
--cc=matthew.garman@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.