From: Alberto Alonso <alberto@ggsys.net>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Implementing low level timeouts within MD
Date: Tue, 30 Oct 2007 00:08:07 -0500 [thread overview]
Message-ID: <1193720887.3876.8.camel@w100> (raw)
In-Reply-To: <1193678521.10336.486.camel@firewall.xsintricity.com>
On Mon, 2007-10-29 at 13:22 -0400, Doug Ledford wrote:
> OK, these you don't get to count. If you run raid over USB...well...you
> get what you get. IDE never really was a proper server interface, and
> SATA is much better, but USB was never anything other than a means to
> connect simple devices without having to put a card in your PC, it was
> never intended to be a raid transport.
I still count them ;-) I guess I just would of hoped for software raid
to really don't care about the lower layers.
>
> > * Internal serverworks PATA controller on a netengine server. The
> > server if off waiting to get picked up, so I can't get the important
> > details.
>
> 1 PATA failure.
I was surprised on this one, I did have good luck with with PATA in
the past. The kernel is whatever came standard in Fedora Core 2
>
> > * Supermicro MB with ICH5/ICH5R controller and 2 RAID5 arrays of 3
> > disks each. (only one drive on one array went bad)
> >
> > * VIA VT6420 built into the MB with RAID1 across 2 SATA drives.
> >
> > * And the most complex is this week's server with 4 PCI/PCI-X cards.
> > But the one that hanged the server was a 4 disk RAID5 array on a
> > RocketRAID1540 card.
>
> And 3 SATA failures, right? I'm assuming the Supermicro is SATA or else
> it has more PATA ports than I've ever seen.
>
> Was the RocketRAID card in hardware or software raid mode? It sounds
> like it could be a combination of both, something like hardware on the
> card, and software across the different cards or something like that.
>
> What kernels were these under?
Yes, these 3 were all SATA. The kernels (in the same order as above)
are:
* 2.4.21-4.ELsmp #1 (Basically RHEL v3)
* 2.6.18-4-686 #1 SMP on a Fedora Core release 2
* 2.6.17.13 (compiled from vanilla sources)
The RocketRAID was configured for all drives as legacy/normal and
software RAID5 across all drives. I wasn't using hardware raid on
the last described system when it crashed.
Alberto
next prev parent reply other threads:[~2007-10-30 5:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:12 Implementing low level timeouts within MD Alberto Alonso
2007-10-26 19:00 ` Doug Ledford
2007-10-27 10:33 ` Samuel Tardieu
2007-10-30 5:19 ` Alberto Alonso
2007-10-30 17:39 ` Doug Ledford
2007-11-01 5:08 ` Alberto Alonso
2007-11-01 14:14 ` Bill Davidsen
2007-11-01 19:16 ` Doug Ledford
2007-11-02 8:41 ` Alberto Alonso
2007-11-02 11:09 ` David Greaves
2007-11-02 17:47 ` Alberto Alonso
2007-11-02 12:44 ` Bill Davidsen
2007-11-02 15:45 ` Doug Ledford
2007-11-02 18:21 ` Alberto Alonso
2007-11-02 19:15 ` Doug Ledford
2007-11-02 21:24 ` Alberto Alonso
2007-10-27 21:46 ` Alberto Alonso
2007-10-27 23:55 ` Doug Ledford
2007-10-28 6:27 ` Alberto Alonso
2007-10-29 17:22 ` Doug Ledford
2007-10-30 5:08 ` Alberto Alonso [this message]
2007-10-30 12:12 ` Gabor Gombas
2007-10-30 17:58 ` Doug Ledford
2007-11-01 14:19 ` Bill Davidsen
2007-11-07 8:47 ` Goswin von Brederlow
2007-10-27 18:59 ` Richard Scobie
[not found] ` <1193522726.7690.31.camel@w100>
2007-10-27 23:46 ` Richard Scobie
2007-10-30 4:47 ` Neil Brown
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=1193720887.3876.8.camel@w100 \
--to=alberto@ggsys.net \
--cc=dledford@redhat.com \
--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.