From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: btrfs raid 5/6
Date: Fri, 01 Dec 2017 16:59:07 +0100 [thread overview]
Message-ID: <1770364.9rtrQ9LI28@eve> (raw)
In-Reply-To: <ffe44495-92f4-c543-9aa4-51227cccc5c9@iinet.net.au>
On Monday, November 27, 2017 11:30:13 PM CET Bill Kenworthy wrote:
> Hi all,
> I need to expand two bcache fronted 4xdisk btrfs raid 10's - this
> requires purchasing 4 drives (and one system does not have room for two
> more drives) so I am trying to see if using raid 5 is an option
>
> I have been trying to find if btrfs raid 5/6 is stable enough to use but
> while there is mention of improvements in kernel 4.12, and fixes for the
> write hole problem I cant see any reports that its "working fine now"
> though there is a phoronix article saying Oracle is using it since the
> fixes.
>
> Is anyone here successfully using btrfs raid 5/6? What is the status of
> scrub and self healing? The btrfs wiki is woefully out of date :(
>
> BillK
I have not seen any indication that BTRFS raid 5/6/.. is usable.
Last status I heard: No scrub, no rebuild when disk failed, ...
It should work as long as all disks stay functioning, but then I wonder why
bother with anything more advanced than raid-0 ?
It's the lack of progress with regards to proper "raid" support in BTRFS which
made me stop considering it and simply went with ZFS.
--
Joost
next prev parent reply other threads:[~2017-12-01 15:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 22:30 [gentoo-user] OT: btrfs raid 5/6 Bill Kenworthy
2017-12-01 15:59 ` J. Roeleveld [this message]
2017-12-01 16:58 ` Wols Lists
2017-12-01 17:14 ` Rich Freeman
2017-12-01 17:24 ` Wols Lists
2017-12-06 23:28 ` Frank Steinmetzger
2017-12-06 23:35 ` Rich Freeman
2017-12-07 0:13 ` Frank Steinmetzger
2017-12-07 0:29 ` Rich Freeman
2017-12-07 21:37 ` Frank Steinmetzger
2017-12-07 21:49 ` Wols Lists
2017-12-07 22:35 ` Frank Steinmetzger
2017-12-07 23:48 ` Wols Lists
2017-12-09 16:58 ` J. Roeleveld
2017-12-09 18:28 ` Wols Lists
2017-12-09 23:36 ` Rich Freeman
2017-12-10 9:45 ` Wols Lists
2017-12-10 15:07 ` Rich Freeman
2017-12-10 21:00 ` Wols Lists
2017-12-11 1:33 ` Rich Freeman
2017-12-11 23:20 ` Frank Steinmetzger
2017-12-12 10:15 ` Neil Bothwick
2017-12-12 12:18 ` Wols Lists
2017-12-12 13:24 ` Neil Bothwick
2017-12-07 7:54 ` Richard Bradfield
2017-12-07 9:28 ` Frank Steinmetzger
2017-12-07 9:52 ` Richard Bradfield
2017-12-07 14:53 ` Frank Steinmetzger
2017-12-07 15:26 ` Rich Freeman
2017-12-07 16:04 ` Frank Steinmetzger
2017-12-07 23:09 ` Rich Freeman
2017-12-07 20:02 ` Wols Lists
2017-12-07 18:35 ` Wols Lists
2017-12-07 20:17 ` Richard Bradfield
2017-12-07 20:39 ` Wols Lists
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=1770364.9rtrQ9LI28@eve \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.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