From: Corey Hickey <bugfood-ml@fatooh.org>
To: linux-raid@vger.kernel.org
Subject: Re: 2.6.20: reproducible hard lockup with RAID-5 resync
Date: Sat, 17 Feb 2007 11:19:44 -0800 [thread overview]
Message-ID: <45D75550.3090905@fatooh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702170613160.8145@p34.internal.lan>
Justin Piszcz wrote:
>> If anyone has any suggestions for further tests I can do, I'll be happy
>> to try them out.
>
> I noticed you are running a disk on /dev/hda, if this is an older mobo and
> you use multiple PCI IDE controllers, if they are in certain slots, or you
> put too many in, they can cause these problems, I have had a few mobos
> that do it if the PCI cards are in a 'certain combination'-- I have had
> this happen with an MSI and ABIT board.
I have a single Promise PCI IDE controller, but I don't have any hard
drives hooked up to it. /dev/hda and all the SATA drives are hooked up
to the onboard nVidia controllers.
My motherboard is a "DFI LanParty UT nf3 250Gb" (despite the unwieldy
name, it's a rather nice board) and I think it dates back to August
2004. I built my machine in November 2004, and I've never had an IDE or
SATA problem with it.
I started testing (and then using) my RAID-5 in May 2006 with Linux
2.6.16. I built the array degraded, so I know that resync worked for me
then. So did restriping, which I did twice. Since then, I've run 2.6.17
and 2.6.19, without any problems.
Thanks,
Corey
next prev parent reply other threads:[~2007-02-17 19:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 6:47 2.6.20: reproducible hard lockup with RAID-5 resync Corey Hickey
2007-02-16 7:59 ` Neil Brown
2007-02-16 8:11 ` Corey Hickey
2007-02-16 21:23 ` Corey Hickey
2007-02-17 10:58 ` Corey Hickey
2007-02-17 11:14 ` Justin Piszcz
2007-02-17 19:19 ` Corey Hickey [this message]
2007-02-18 9:51 ` Corey Hickey
2007-02-18 21:09 ` Corey Hickey
2007-02-18 22:04 ` Neil Brown
2007-02-19 0:06 ` Corey Hickey
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=45D75550.3090905@fatooh.org \
--to=bugfood-ml@fatooh.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 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).