From: Robert Hancock <hancockrwd@gmail.com>
To: Randy Broman <rbroman@bayarea.net>
Cc: linux-ide@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: Software RAID Problem
Date: Wed, 29 Jul 2009 13:40:17 -0600 [thread overview]
Message-ID: <4A70A5A1.1030600@gmail.com> (raw)
In-Reply-To: <4A706D78.7000107@bayarea.net>
On 07/29/2009 09:40 AM, Randy Broman wrote:
> Per your instructions .... I tail -f'd /var/log/dmesg and
> /var/l0g/messages,
> and then executed the four mdadm commands below, for the faulty array.
> After removing and re-adding the faulty disk partition to the array, the
> array
> returns to faulty state almost immediately. During the process, dmesg
> didn't
> show anything, but the information written to /var/log/messages is at the
> bottom hereto.
>
> I suppose one answer is that there's a hardware issue with the array, or
> one of the disks. But that would be surprising to me - both the hardware
> array and the disks are new, and the setup (hardware/software/RAID) worked
> fine until I tried to upgrade my kernel. Possibly RAID-related formats are
> different between kernel 2.6.28 and 2.6.31????
>
> Anyway, would appreciate diagnosis/recommendations ...
The output looks a bit scrambled and seems to be missing certain lines
(we see hardresets but not any error that triggered it). Sometimes that
seems to happen if disk problems are occurring (kernel logger buffer
overflows or something). If the kernel messages are showing up in
/var/log/messages then they should be showing up in dmesg and would be
more complete. Can you check again?
next prev parent reply other threads:[~2009-07-29 19:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 16:24 Software RAID Problem rbroman
2009-07-29 2:09 ` Tejun Heo
2009-07-29 15:40 ` Randy Broman
2009-07-29 19:40 ` Robert Hancock [this message]
2009-07-29 20:43 ` Randy Broman
-- strict thread matches above, loose matches on Subject: below --
2009-07-27 20:27 Randy Broman
2009-07-28 3:19 ` Tejun Heo
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=4A70A5A1.1030600@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rbroman@bayarea.net \
--cc=tj@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).