From: David Greaves <david@dgreaves.com>
To: Paul VanGundy <pvangundy@bradfordnetworks.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Kernel Module - Raid
Date: Mon, 05 Nov 2007 21:16:58 +0000 [thread overview]
Message-ID: <472F884A.4010602@dgreaves.com> (raw)
In-Reply-To: <472F840F.2060607@bradfordnetworks.com>
Paul VanGundy wrote:
> Thanks for the prompt replay David. Below are the answers to your questions:
>
>> What hardware/distro etc are you using?
>> Is this an expensive (hundreds of £) card? Or an onboard/motherboard chipset?
> The distro is Suse 10.1.
As a bit of trivia, Neil (who wrote and maintains linux RAID) works for Suse.
> It is an onboard chipset.
In which case it's not likely to be hardware RAID.
See: http://linux-ata.org/faq-sata-raid.html
>> Once you answer this then it may be worth suggesting using sw-raid (in which
>> case we can help out) or pointing you elsewhere...
You should probably configure the BIOS to use
>> That's one of the big reasons proprietary drivers suck on linux.
>
> Ok. So this chipset has the ability to use an Intel based RAID. Would
> that be better?
mmm, see the link above...
In almost any case where you are considering 'onboard' raid, linux software raid
(using md and mdadm) is a better choice.
Start here: http://linux-raid.osdl.org/index.php/Main_Page
(feel free to correct it or ask here for clarification)
Also essential reading is the mdadm man page.
David
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-11-05 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 20:19 Kernel Module - Raid Paul VanGundy
2007-11-05 20:48 ` David Greaves
2007-11-05 20:58 ` Paul VanGundy
2007-11-05 21:16 ` David Greaves [this message]
2007-11-07 16:51 ` Paul VanGundy
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=472F884A.4010602@dgreaves.com \
--to=david@dgreaves.com \
--cc=linux-raid@vger.kernel.org \
--cc=pvangundy@bradfordnetworks.com \
/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.