From: "Marcin M. Jessa" <lists@yazzy.org>
To: linux-raid@vger.kernel.org
Subject: How to stress test an RAID 6 array?
Date: Mon, 03 Oct 2011 15:26:53 +0200 [thread overview]
Message-ID: <4E89B81D.5000800@yazzy.org> (raw)
Hi guys.
After a rather long thread with many questions about my failed RAID
array I'm trying to give it another shot.
I replaced all the SATA cables and I want to stress test my array.
Short description of what it was used for when it failed:
I had a 5 drive (5x2TB Seagate Green Barracuda) RAID 6 array with LVM on
top of it.
- One of the LVs was serving as a samba storage
- One as a NFS exported storage with web sites
- 3 LVs had KVM hosts installed to them (heavy hammered web server,
MySQL server and mail/imap/pop3 server)
The load seemed to have stressed my array/the HDs to the point when 3 of
the drives were kicked off the array resulting in loss of data.
It's hard to find a cause of it - some forum threads on the Interner
suggest it may be the kernel, some say it could be the SATA controller,
the SATA cables and most of them suggest it's because of the hard drives.
Now I would like to stress test the array and see whether it would fail
again or not. What would be the best way to do that?
--
Marcin M. Jessa
next reply other threads:[~2011-10-03 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 13:26 Marcin M. Jessa [this message]
2011-10-03 13:39 ` How to stress test an RAID 6 array? 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
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=4E89B81D.5000800@yazzy.org \
--to=lists@yazzy.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.