From: David Brown <david@westcontrol.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Mon, 02 Apr 2012 08:59:36 +0200 [thread overview]
Message-ID: <jlbj87$8fr$1@dough.gmane.org> (raw)
In-Reply-To: <4F784A06.1@anonymous.org.uk>
On 01/04/2012 14:28, John Robinson wrote:
> On 01/04/2012 11:33, David Brown wrote:
> [...]
>> For an application like this, it would probably make sense to put the
>> xfs log (and the mdraid bitmap file, if you are using one) on a separate
>> disk - perhaps a small SSD.
>
> Now that you've suggested that, it occurs to me that for an application
> like this, the OP might be better doing his multiple slow streams to a
> spool folder on SSD, and copying over to the big array of spinning rust
> when each stream completes. 200 streams of 500MB is 100GB of data, so a
> pair of slightly larger SSDs in RAID1 (or RAID10, to balance the reads
> coming off) would do nicely as a spool area.
If the OP wants to do that, he must be careful when looking at the rated
write speeds for the SSDs. SSDs need a bit of a break on occasion to
get time to do their garbage collection - their long-term streamed write
speed is therefore lower than their short-term write speeds (and that's
the figure that will be given in the spec). But if you take that into
account, and short-partition the SSD's a little (i.e., leave 10%
unpartitioned, and put the raid1 on the partition rather than the disk)
so that there are always plenty of free blocks when they are needed,
that could be a very good solution.
>
> This might also be a good application for bcache, FlashCache or whatever.
>
> Cheers,
>
> John.
>
next prev parent reply other threads:[~2012-04-02 6:59 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 [this message]
[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
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='jlbj87$8fr$1@dough.gmane.org' \
--to=david@westcontrol.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).