From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Which raid card to buy for Sarge
Date: Thu, 01 Apr 2004 09:56:40 +0400 [thread overview]
Message-ID: <406BAF18.8010005@wasp.net.au> (raw)
In-Reply-To: <406BAC2F.8090407@pobox.com>
Jeff Garzik wrote:
>> With the Highpoint driver I get a drive failure and the card starts
>> beeping. I fire up the management util, remove the faulty drive, swap
>> it out and insert the new drive in the array. The array starts
>> rebuilding - no effect on the uptime and only a slight loss in
>> throughput. Plus it's seamless.
>
>
> Yeah, md+mdadm can do all this right now, provided the hardware and
> driver support is there...
>
Yes, my point however is for low budget stuff with software raid the driver support is not yet there
in a vanilla kernel.
I can't just whack a sata drive off one of my promise SATA150-TX4 controllers, pop another one in
and have the kernel rescan the partition table and realise a new drive was present. (YET!)
My entire point was that for the types of controllers that were being discussed (Highpoint was
particularly mentioned, but you can really interchange any multi-port ATA/SATA controller for this)
that the kernel support was not there *yet* but hardware raid or faux hardware raid will buy you
this support *now*.
Regards,
Brad
next prev parent reply other threads:[~2004-04-01 5:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 15:47 Which raid card to buy for Sarge me
2004-03-31 16:15 ` Luca Berra
2004-03-31 16:43 ` me
2004-03-31 16:58 ` Måns Rullgård
2004-03-31 18:03 ` Ralph Paßgang
2004-03-31 19:50 ` Mark Hahn
2004-03-31 20:19 ` Richard Scobie
2004-04-01 9:07 ` KELEMEN Peter
2004-04-04 4:47 ` Richard Scobie
2004-04-09 11:16 ` KELEMEN Peter
2004-04-09 13:07 ` Which raid card to buy for SargeD Yu Chen
2004-04-09 21:52 ` KELEMEN Peter
2004-03-31 20:42 ` Which raid card to buy for Sarge Ralph Paßgang
2004-03-31 20:59 ` Jeff Garzik
2004-03-31 21:39 ` Guy
2004-04-01 4:49 ` Brad Campbell
2004-04-01 4:51 ` seth vidal
2004-04-01 5:01 ` Brad Campbell
2004-04-01 5:39 ` Guy
2004-04-01 5:51 ` Brad Campbell
2004-04-01 5:29 ` Guy
2004-04-01 5:54 ` Jeff Garzik
2004-04-01 5:44 ` Jeff Garzik
2004-04-01 5:56 ` Brad Campbell [this message]
2004-04-01 7:49 ` Sandro Dentella
2004-04-01 8:03 ` Brad Campbell
2004-04-01 8:07 ` Jeff Garzik
2004-04-16 14:25 ` Nick Maynard
2004-04-16 15:09 ` Måns Rullgård
2004-04-16 16:29 ` Nick Maynard
2004-04-16 17:44 ` Måns Rullgård
2004-04-16 22:34 ` jlewis
2004-04-01 4:24 ` me
2004-04-01 4:57 ` Clemens Schwaighofer
2004-04-01 5:34 ` Jeff Garzik
2004-04-01 6:39 ` Clemens Schwaighofer
2004-04-01 5:58 ` Jeff Garzik
2004-04-01 12:52 ` me
2004-04-01 19:31 ` Terrence Martin
2004-04-02 4:46 ` me
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=406BAF18.8010005@wasp.net.au \
--to=brad@wasp.net.au \
--cc=jgarzik@pobox.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 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).