From: John Robinson <john.robinson@anonymous.org.uk>
To: Jack Wang <jack.wang.usish@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Mon, 02 Apr 2012 11:28:22 +0100 [thread overview]
Message-ID: <4F797F46.10600@anonymous.org.uk> (raw)
In-Reply-To: <CA+res+SSJ49cPubOdmXi6Z3jnE+4wzsh1MJehs78U82e3iDhaA@mail.gmail.com>
On 02/04/2012 11:01, Jack Wang wrote:
> 2012/4/2 John Robinson<john.robinson@anonymous.org.uk>
>> On 02/04/2012 04:15, Jack Wang wrote:
>>> 2012/4/1 John Robinson<john.robinson@anonymous.org.uk
>>> <mailto:john.robinson@anonymous.org.uk>>
>> [...]
>>> This might also be a good application for bcache, FlashCache or
>>> whatever.
>>>
>>> Using bcache/flashcache is what I'm considering, does above
>>> configuration option still needed?
[...]
> Thanks for reply , I mean using SSD as cache device, and raid5
> 16*7200rpm disks, is this works for streaming workload above?
>
> I know bcache is try to turn rand write to seqencial write, but most
> ssd is not good at RAND write as I know.
I don't know where you got that from; SSDs are absolutely brilliant at
small random writes and reads, hundreds of times better than spinning
hard discs. bcache and flashcache were written specifically to take
advantage of SSDs' high I/Os per second for small (random) reads and writes.
I wouldn't touch RAID5 for anything other than 3 drives; I'd use RAID6
or RAID60 for 4-plus where I didn't need the better small/random write
performance of RAID10. I haven't actually used bcache or flashcache,
which is why I introduced them with "might".
My fantasy configuration in your 16-drive chassis would be 2 6-drive
RAID6s, striped together in RAID0, with an SSD cache over the top built
from two SSDs in RAID10 (or if I was feeling really paranoid, 3 SSDs in
RAID10,n3), with the remaining slot containing a hot spare for the RAID6s.
Cheers,
John.
next prev parent reply other threads:[~2012-04-02 10:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 1:22 RAID5 created by 8 disks works with xfs daobang wang
2012-03-31 7:59 ` Mathias Burén
2012-03-31 20:09 ` Stan Hoeppner
2012-04-01 1:16 ` daobang wang
2012-04-01 2:05 ` daobang wang
2012-04-01 5:13 ` Stan Hoeppner
2012-04-01 3:51 ` Stan Hoeppner
2012-04-01 5:12 ` daobang wang
2012-04-01 5:40 ` Stan Hoeppner
2012-04-01 5:59 ` daobang wang
2012-04-01 6:20 ` daobang wang
2012-04-01 7:08 ` Marcus Sorensen
2012-04-02 3:47 ` Stan Hoeppner
2012-04-05 0:48 ` daobang wang
[not found] ` <CACwgYDOtCoVF-p+KKqPYxHhA4vWF78Ueecx9hcVWLoyxFWzV9Q@mail.gmail.com>
2012-04-05 21:01 ` Stan Hoeppner
2012-04-06 0:25 ` daobang wang
2012-04-06 2:33 ` daobang wang
2012-04-06 6:00 ` Jack Wang
2012-04-06 6:45 ` daobang wang
2012-04-06 6:49 ` daobang wang
2012-04-06 8:18 ` Stan Hoeppner
2012-04-06 8:45 ` daobang wang
2012-04-06 11:12 ` Stan Hoeppner
2012-04-18 2:23 ` daobang wang
2012-04-02 3:12 ` Stan Hoeppner
2012-04-01 10:33 ` David Brown
2012-04-01 12:28 ` John Robinson
2012-04-02 6:59 ` David Brown
[not found] ` <CA+res+QkLi7sxZrD-XOcbR47CeJ5gADf7P6pa1w1oMf8CKSB4g@mail.gmail.com>
2012-04-02 8:01 ` John Robinson
2012-04-02 10:01 ` Jack Wang
2012-04-02 10:28 ` John Robinson [this message]
2012-04-02 20:41 ` Stan Hoeppner
2012-04-02 5:43 ` Stan Hoeppner
2012-04-02 7:04 ` David Brown
2012-04-02 20:21 ` Stan Hoeppner
2012-04-01 4:52 ` Stan Hoeppner
2012-04-01 8:06 ` John Robinson
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=4F797F46.10600@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=jack.wang.usish@gmail.com \
--cc=linux-raid@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).