From: Roman Mamedov <rm@romanrm.net>
To: George Duffield <forumscollective@gmail.com>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Understanding BTRFS storage
Date: Fri, 28 Aug 2015 14:46:43 +0500 [thread overview]
Message-ID: <20150828144643.7074ed9e@natsu> (raw)
In-Reply-To: <CAG__1a4x_bv2DURyT0ZW0p+udh43ifcn=bHjUKM4NF1Tk=cYDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Fri, 28 Aug 2015 10:50:12 +0200
George Duffield <forumscollective@gmail.com> wrote:
> Running a traditional raid5 array of that size is statistically
> guaranteed to fail in the event of a rebuild.
Yeah I consider RAID5 to be safe up to about 4 devices. As you already have 5
and looking to expand, I'd recommend going RAID6. The "fail on rebuild" issue
is almost completely mitigated by it, perhaps up to a dozen of drives or more.
Don't know about your usage scenarios, but as for me the loss of storage
efficiency in RAID10 compared to RAID6 in unacceptable, and I also don't need
the performance benefits of RAID10 at all.
So both from the efficiency and stability standpoints my personal choice
currently is Btrfs single device mode on top of MD RAID5 (in a 4 drive array)
and RAID6 (with 7 drives).
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-08-28 9:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 8:56 Understanding BTRFS storage George Duffield
2015-08-26 11:41 ` Austin S Hemmelgarn
2015-08-26 11:50 ` Hugo Mills
2015-08-26 11:50 ` Roman Mamedov
2015-08-26 12:03 ` Austin S Hemmelgarn
2015-08-27 2:58 ` Duncan
2015-08-27 12:01 ` Austin S Hemmelgarn
2015-08-28 9:47 ` Duncan
2015-08-28 12:54 ` Austin S Hemmelgarn
2015-08-28 8:50 ` George Duffield
2015-08-28 9:35 ` Hugo Mills
2015-08-28 15:42 ` Chris Murphy
2015-08-28 17:11 ` Austin S Hemmelgarn
2015-08-29 8:52 ` George Duffield
2015-08-29 22:28 ` Chris Murphy
2015-09-02 5:01 ` Russell Coker
2015-08-28 9:46 ` Roman Mamedov [this message]
2015-08-26 11:50 ` 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=20150828144643.7074ed9e@natsu \
--to=rm@romanrm.net \
--cc=ahferroin7@gmail.com \
--cc=forumscollective@gmail.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).