linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maarten van den Berg <maarten@vbvb.nl>
To: linux-raid@vger.kernel.org
Subject: Re: I'm about ready to do SW-Raid5 - pointers needed
Date: Tue, 28 Oct 2003 15:06:32 +0100	[thread overview]
Message-ID: <200310281506.32013.maarten@vbvb.nl> (raw)
In-Reply-To: <Pine.LNX.4.56.0310280749080.23689@unicorn.drogon.net>

On Tuesday 28 October 2003 09:26, Gordon Henderson wrote:
> On Mon, 27 Oct 2003, berk walker wrote:

> Good luck with your promise board (what type is it?) I've had a lot of
> problems with them (kernels 2.4.20-22) They seem to work, but under heavy
> load, I see processes getting stuck in "D" state (eg. nfsd or anything
> doing lots of disk IO) Most of the time they recover, but I've load a disk
> partition on more than one occasion (saved by raid, and it re-built OK
> after a reboot). I've seen this in 2 different servers and tried both
> Intel and AMD CPUs. Tonight I try a set of different PCI IDE controllers
> in one server to see if that helps it.

Promise cards do suck somewhat -albeit I use them- but what else is there ? 
The highpoint-equipped cards are even more sucky in many cases.

> It's hard to tell if it's a real hardware problem or a software one (the
> Promise driver being fairly new, patched in at 2.4.20, included in 2.4.22)

Ehm, what ???  You're probably talking about the driver for the fasttrack 
cards who are -in their own respect- raid cards. But if you use a 'plain' 
card like the ultra it's just used as an additional IDE channel. That has 
worked long long before 2.4.20 and it is what I use.  No sense in buying a 
pricey fasttrack if you're not going to use the raid but use the md tools 
instead.

Regards,
Maarten

-- 
Yes of course I'm sure it's the red cable. I guarante[^%!/+)F#0c|'NO CARRIER

  reply	other threads:[~2003-10-28 14:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 23:42 I'm about ready to do SW-Raid5 - pointers needed berk walker
2003-10-28  0:37 ` David Anderson
2003-10-28  1:55   ` maarten van den Berg
2003-10-28  3:32     ` rob
2003-10-28  5:37     ` Luke Rosenthal
2003-10-28  8:20       ` Spinning down disks [Re: I'm about ready to do SW-Raid5 - pointers needed] Gordon Henderson
2003-10-28  8:39       ` I'm about ready to do SW-Raid5 - pointers needed Hermann Himmelbauer
2003-10-28  1:07 ` maarten van den Berg
2003-10-28  1:21   ` David Anderson
2003-10-28  1:35     ` maarten van den Berg
2003-10-28  1:55       ` David Anderson
2003-10-28  1:58       ` David Anderson
2003-10-28  8:23 ` Hermann Himmelbauer
2003-10-28  8:26 ` Gordon Henderson
2003-10-28 14:06   ` maarten van den Berg [this message]
2003-10-28 14:25     ` Gordon Henderson
2003-10-28 15:05       ` maarten van den Berg
2003-10-28 15:10         ` Gordon Henderson
2003-10-28 16:37         ` Norman Schmidt
2003-10-28 16:54           ` Gordon Henderson
2003-10-28 18:28     ` jlewis
2003-10-28 19:14       ` Gordon Henderson
2003-10-29  4:33         ` Maurice Hilarius
2003-10-28 19:51       ` maarten van den Berg

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=200310281506.32013.maarten@vbvb.nl \
    --to=maarten@vbvb.nl \
    --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).