From: Hans Kraus <hans@hanswkraus.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: RAID 6 stable?
Date: Sat, 19 Jan 2019 17:07:01 +0100 [thread overview]
Message-ID: <c41a1da0-9986-413d-6b22-4183188fd8aa@hanswkraus.com> (raw)
Hi,
after a posting in the linux-btrfs mailing list I stumbled across
<https://btrfs.wiki.kernel.org/index.php/Project_ideas#Raid5.2F6>.
Does that mean that BTRFS RAID6 is free of known errors and ready for
deployment on data servers?
If not: is there an estimation (time-wise) when RAID6 is ready?
The background of my question: I have to rebuild my samba server which
ran out of storage. I'm using currently efs4 on top of mdadm RAID6.
I would prefer to rebuild it with BTRFS. I can postpone that rebuild
for some months.
A second question: the ZFS docu recommends very strongly to use ECC
memory on machines with ZFS RAID-Zn. Holds these arguments true for
BTRFS as well?
Kind regards,
Hans
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next reply other threads:[~2019-01-19 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 16:07 Hans Kraus [this message]
2019-01-19 20:34 ` RAID 6 stable? Andrei Borzenkov
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=c41a1da0-9986-413d-6b22-4183188fd8aa@hanswkraus.com \
--to=hans@hanswkraus.com \
--cc=linux-btrfs@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 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).