From: "Marcin M. Jessa" <lists@yazzy.org>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: How to stress test an RAID 6 array?
Date: Mon, 03 Oct 2011 15:58:11 +0200 [thread overview]
Message-ID: <4E89BF73.8020604@yazzy.org> (raw)
In-Reply-To: <CADNH=7E9n-uj-xNPq-DuYgfJ+Js9b4bWn_QyeDJ8O+ka4GjLiQ@mail.gmail.com>
On 10/3/11 3:39 PM, Mathias Burén wrote:
> I would run badblocks on the md0 device. (increase number of blocks to
> check at a time until you use all your available RAM)
> After that I'd run dd.
Any particular options you would give to dd ?
> I would also check the SMART data on all
> drives
What's strange SMART always says all the drives are healthy.
All of failures started with dmesg saying:
exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata9.00: failed command: FLUSH CACHE EXT
ata9.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata9.00: status: { DRDY }
That "exception Emask" part pointed me to misc threads where people
mentioned bugs in the Linux kernel.
A reboot would somehow reset the drives and they would always be working
fine again and I could always resync the array until the next time when
a drive would get kicked off.
> and the health of the controller.
How can I run a check on that within Linux?
--
Marcin M. Jessa
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-03 13:58 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 [this message]
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=4E89BF73.8020604@yazzy.org \
--to=lists@yazzy.org \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
/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.