linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Luter <luterac@bellsouth.net>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 problem with multiple Promise PDC20269 controllers
Date: Tue, 29 Oct 2002 14:02:30 -0600	[thread overview]
Message-ID: <20021029200230.GG21099@smeagol> (raw)
In-Reply-To: <200210291908.35581.roy@karlsbakk.net>

I've had problems with using two PDC20269's at the same time too.
(well actually one is a 69, the other is the 100, not 133 version).

They seem to work ok without DMA on, but otherwise I get lots of dma
errors when heavy load is placed (such as re-syncing).

I've got an Epox motherboard (Duron 1.0 ghz), and four IBM 7200RPM
120gig harddrives.

Right now things are running "ok" by having all four drives on one
card and the other card (doesn't matter which) in my desk drawer.  But
it would be nice if I could put it back in the system (the speed was
-great-!).

-Gryn

On Tue, Oct 29, 2002 at 07:08:35PM +0100, Roy Sigurd Karlsbakk wrote:
> On Monday 28 October 2002 16:17, Chris Hirsch wrote:
> > This is probably more of a hardware question than RAID but since there
> > has to be somebody in the same boat as myself....
> >
> > I'm trying to do a RAID5 setup with 3 IDE disks connected to IDE1/IDE2
> > on a Promise  ULTRA133 TX2. Fine..works great with only two disks. So I
> > bring in my 3rd disk on the second PDC20269 and I get kernel lockups and
> > fun stuff when the array tries to rebuild or activate. I've tried deja
> > and there seems to be some issues with multiple cards but I can't seem
> > to find any resolutions. This is a RH 8.0 box using 2.4.18.
> 
> strange ...
> 
> I'm running 20269's (or was that 68's?) with four drives each, and it works 
> fine

      reply	other threads:[~2002-10-29 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28 15:17 RAID5 problem with multiple Promise PDC20269 controllers Chris Hirsch
2002-10-29 18:08 ` Roy Sigurd Karlsbakk
2002-10-29 20:02   ` Adam Luter [this message]

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=20021029200230.GG21099@smeagol \
    --to=luterac@bellsouth.net \
    --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).