From: Wols Lists <antlists@youngman.org.uk>
To: Stan Hoeppner <stan@hardwarefreak.org>,
Benjammin2068 <benjammin2068@gmail.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommendation on new system Arrays
Date: Sun, 8 Jan 2017 09:07:10 +0000 [thread overview]
Message-ID: <5872013E.6000801@youngman.org.uk> (raw)
In-Reply-To: <db381235-8eb9-3efe-2346-110c13af48d7@hardwarefreak.org>
On 08/01/17 04:13, Stan Hoeppner wrote:
>>>
>>> This sounds like one of the few use cases where they might be a good
>>> idea. Worth considering, at least. Might even work well in your planned
>>> raid-6 config.
>>>
>> Yea, I thought about that too. So you're suggesting a RAID1 consisting
>> of (2) RAID6 arrays.
> That's not sane. RAID 10, or more precisely, RAID 0 over many RAID 1
> pairs, will yield more usable capacity and without the parity penalty or
> RMW cycles.
I was actually thinking pure raid-6. Which was Benjammin's original
idea. The thing to bear in mind is that for these drives, rewrite
performance is going to be abysmal, but in this particular scenario
rewriting is going to be unusual, anyway. What we *don't* want with
these drives is RMW.
It's just struck me, this might be where it's worth sticking a small SSD
in front of the array as a journal, and flagging these drives as "write
mostly". But I'm not sure whether this functionality is yet standard or
are the devs still working on it?
Cheers,
Wol
next prev parent reply other threads:[~2017-01-08 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 16:14 Recommendation on new system Arrays Benjammin2068
2017-01-07 10:04 ` Wols Lists
2017-01-08 4:04 ` Benjammin2068
2017-01-08 4:13 ` Stan Hoeppner
2017-01-08 9:07 ` Wols Lists [this message]
2017-01-12 15:39 ` Phil Turmel
2017-01-17 18:57 ` Benjammin2068
[not found] ` <d1f5b65b-5a0b-92e1-7fe7-d2a0c45c8998@fnarfbargle.com>
2017-01-10 8:48 ` Benjammin2068
2017-01-10 15:55 ` 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=5872013E.6000801@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=benjammin2068@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=stan@hardwarefreak.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).