From: Samuel Flory <sflory@rackable.com>
To: Wakko Warner <wakko@animx.eu.org>
Cc: Tomas Szepe <szepe@pinerecords.com>, linux-kernel@vger.kernel.org
Subject: Re: Best Low-cost IDE RAID Solution For 2.6.x? (OT?)
Date: Tue, 30 Dec 2003 12:58:59 -0800 [thread overview]
Message-ID: <3FF1E713.9050001@rackable.com> (raw)
In-Reply-To: <20031230094157.A7191@animx.eu.org>
Wakko Warner wrote:
>>>>nice about bad sectors as most hardware raid controllers. On the other
>>>>hand the md driver kicks the ass of nearly every raid controller I've tried.
>>>
>>>Faster than the mylex extreme raid 2000? or one of the higher end adaptecs?
>>
>>Even faster than HP/Compaq cciss hwraid setups, yes.
>
>
> I've personally not had any experience with any hardware raid other than the
> mylex DAC960 family.
>
I know a number of people that run their mylex cards in jbod mode and
use software raid;-)
> One thing that keeps me from using the linux raid sw is the fact it can't be
> partitioned.
You're thinking of it the wrong way. You just create a bunch of
partitions and make them into raid devices. You shouldn't be using the
entire disk or you will break autodetection.
> I thought about lvm/evms, but I'm unwilling to make an initrd to
> set it up (mounting root). Unfortunately boot loaders don't seem to support
> anything other than raid1. (Mostly lilo, but I'm not sure grub would do this
> either)
>
Lilo deals well with raid 1 devices. I typical create a small raid 1
mirror as /boot. Just be sure to install your bootloader on to all
drives. Newer versions of lilo will do the right thing if told to use
/dev/mdwhatever.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-12-30 20:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 18:04 Best Low-cost IDE RAID Solution For 2.6.x? (OT?) Johannes Ruscheinski
2003-12-28 18:50 ` Joel Jaeggli
2003-12-28 21:35 ` Johannes Ruscheinski
2003-12-28 21:45 ` Arjan van de Ven
2003-12-28 22:14 ` Johannes Ruscheinski
2003-12-28 23:05 ` H. Peter Anvin
2003-12-29 1:18 ` Wakko Warner
2003-12-28 21:56 ` bert hubert
2003-12-28 23:36 ` Joel Jaeggli
2004-01-07 23:28 ` bill davidsen
2003-12-29 2:10 ` Samuel Flory
2003-12-29 13:41 ` Tomas Szepe
2003-12-29 18:59 ` Johannes Ruscheinski
2003-12-29 19:04 ` Samuel Flory
2003-12-29 19:06 ` Tomas Szepe
2003-12-30 0:03 ` Wakko Warner
2003-12-30 6:54 ` Tomas Szepe
2003-12-30 14:41 ` Wakko Warner
2003-12-30 20:58 ` Samuel Flory [this message]
2004-01-07 23:35 ` bill davidsen
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=3FF1E713.9050001@rackable.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
--cc=wakko@animx.eu.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.