From: Nathan Hunsperger <linux-raid@hunsperger.com>
To: Tom Maddox <tmaddox@thereinc.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Bizarre RAID "failure"
Date: Fri, 20 Feb 2004 00:33:27 -0800 [thread overview]
Message-ID: <20040220083327.GB5535@munchnet.com> (raw)
In-Reply-To: <1077230692.28817.485.camel@s8n-1.thereinc.com>
On Thu, Feb 19, 2004 at 02:44:52PM -0800, Tom Maddox wrote:
<SNIP>
> If the system goes down unexpectedly (e.g., because of a power failure),
> the RAID array comes back up dirty and begins to rebuild itself, which
> is odd enough on its own. What's worse is that, whenever this happens,
> the rebuild hangs at about 2.4%. When it reaches that point, the array
> becomes totally nonresponsive--I can't even query its status with mdadm
> or any other tool, although I can use "cat /proc/mdstat" to see the
> status of the rebuild. Any command that attempts to access the RAID
> drive hangs.
<SNIP>
> Has anyone seen this behavior before, and can you recommend a solution?
Tom,
I have had problems very similar to this before. I was running 14 fibre
channel disks on a QLA2100 HBA w/ various 2.4 kernels. What I found
was that after a while of heavy IO, all access to the disks stopped,
and the rebuild would hang. Additionally, any command that required
access to any filesystem data that wasn't cached (on any filesystem)
would hang. By switching between the 3 or so available QLA drivers,
I could affect the delta between reboot and stall. I knew the hardware
was fine, as it worked flawlessly under Solaris. In the end, I had
to upgrade the HBA to a QLA2200, at which time I had no more problems.
Because the hardware works under different OSs, I have to believe that
my problem was an incompatability between the QLA2100 and the drivers
(even though they claimed to work for it).
I hope that at least gives you some possible insight.
- Nathan
>
> Thanks,
>
> Tom
>
> -
> 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:[~2004-02-20 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 22:44 Bizarre RAID "failure" Tom Maddox
2004-02-19 23:38 ` Måns Rullgård
2004-02-20 0:39 ` Kanoa Withington
2004-02-20 0:44 ` Tom Maddox
2004-02-20 8:33 ` Nathan Hunsperger [this message]
2004-03-02 16:56 ` Corey McGuire
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=20040220083327.GB5535@munchnet.com \
--to=linux-raid@hunsperger.com \
--cc=linux-raid@vger.kernel.org \
--cc=tmaddox@thereinc.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 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).