From: "Phantazm" <phantazm@phantazm.nu>
To: linux-raid@vger.kernel.org
Subject: Re: Huge mdadm resync problem.
Date: Thu, 17 Feb 2005 15:57:12 +0100 [thread overview]
Message-ID: <cv2b71$q83$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.56.0502171435420.819@lion.drogon.net
It might be worht a try. I have 6 pci slots. That i know of today my mobo
shares irq on pci 5 and 2. looks like i cant get around that.
I have disabled apic on mobo too.
Going to see if i can get me 2 more ata133 cards then to see if i get more
lucky :)
Thanx for your answers and suggestions.
"Gordon Henderson" <gordon@drogon.net> skrev i meddelandet
news:Pine.LNX.4.56.0502171435420.819@lion.drogon.net...
> On Thu, 17 Feb 2005, Phantazm wrote:
>
>> I use master slave. Problem is that i cant break raid set couse if i do i
>> will loose over 1TB of data :/
>>
>> Goin to see if i can get more controller cards though.
>
> Do it. Use 4 2-port cards for your 8 drives and only one drive per cable.
> It is possible, and I've had it happen to me, that a hardware failure on a
> failing drive can cause loss of access to the 2nd drive on the same cable.
> Fortunately when it happened to me, the disks weren't in a RAID set and I
> didn't lose any data on the other drive, but if the disks were in a RAID
> set, then you'd have a 2-disk failure on your hands, and unless it was
> RAID-6, then you'd be shafted!
>
> I was about to suggest running with noapic, but you've already tried
> that... You might also want to see if the motherboard has a way to turn
> the APIC off too. I had that on one Athlon mobo, and running it all in PIC
> mode kept it going much better.
>
> Also experiment with PCI slot locations, although with 4 PCI cards, you
> might not have much luck, depending on your motherboard. Try to get each
> card on its own interrupt if at all possible. Some BIOSes can help fix
> this for you, some can't....
>
> Gordon
> -
> 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:[~2005-02-17 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 13:52 Huge mdadm resync problem Lord Hess,Raum 301Kw,54-8994
2005-02-17 14:33 ` Phantazm
2005-02-17 14:40 ` Gordon Henderson
2005-02-17 14:57 ` Phantazm [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-17 12:08 Phantazm
2005-02-17 12:37 ` Phantazm
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='cv2b71$q83$1@sea.gmane.org' \
--to=phantazm@phantazm.nu \
--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.