From: "Marcin M. Jessa" <lists@yazzy.org>
To: Joe Landman <joe.landman@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How to stress test an RAID 6 array?
Date: Mon, 03 Oct 2011 22:35:28 +0200 [thread overview]
Message-ID: <4E8A1C90.9050802@yazzy.org> (raw)
In-Reply-To: <4E89C580.8050603@gmail.com>
On 10/3/11 4:24 PM, Joe Landman wrote:
[...]
> nohup ./loop_check.pl 10 > out 2>&1 &
>
> which will execute the fio against sw_check.fio 10 times. Each
> sw_check.fio run will write and check 512GB of data (4 jobs, each
> writing and checking 128 GB data). Go ahead and change that if you want.
> We use a test just like this in our system checkout pipeline.
>
> This *will* stress all aspects of your units very hard. If you have an
> error in your paths, you will see crc errors in the output. If you have
> a marginal RAID system, this will probably kill it. Which is good, as
> you'd much rather it die on a hard test like this than in production.
>
> You can ramp up the intensity by increasing the number of jobs, or the
> size of the io, etc. We can (and do) crash machines with horrific loads
> generated from similar tests, just to see where the limits of the
> machines are at, and to help us tweak/tune our kernels for best
> stability under these horrific loads. The base test is used to convince
> us that the RAID is stable though.
I replaced SATA cables, updated the BIOS to the very last version,
ran/put hdparm -S0 /dev/sd[a-m] to /etc/rc.local and reset the BIOS to
default settings.
It's running now and nothing broke so far.
Would it be enough to run one check with the sw_check.fio (I just
changed the mount path) from your website to determine whether the RAID
holds or not?
--
Marcin M. Jessa
next prev parent reply other threads:[~2011-10-03 20:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 13:26 How to stress test an RAID 6 array? Marcin M. Jessa
2011-10-03 13:39 ` Mathias Burén
2011-10-03 13:58 ` Marcin M. Jessa
2011-10-03 14:03 ` Mathias Burén
2011-10-03 14:18 ` Marcin M. Jessa
2011-10-03 14:29 ` Mathias Burén
2011-10-03 15:17 ` Marcin M. Jessa
2011-10-04 4:42 ` Stan Hoeppner
2011-10-04 3:56 ` Stan Hoeppner
2011-10-04 8:37 ` Marcin M. Jessa
2011-10-05 17:41 ` Stan Hoeppner
2011-10-03 14:24 ` Joe Landman
2011-10-03 15:40 ` Marcin M. Jessa
2011-10-03 20:35 ` Marcin M. Jessa [this message]
2011-10-03 16:16 ` maurice
2011-10-08 14:44 ` Gordon Henderson
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=4E8A1C90.9050802@yazzy.org \
--to=lists@yazzy.org \
--cc=joe.landman@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).