From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adam Kropelin <akropel1@rochester.rr.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
marc@perkel.com
Subject: Re: Linux: Why software RAID?
Date: Thu, 24 Aug 2006 14:20:50 +0100 [thread overview]
Message-ID: <1156425650.3007.140.camel@localhost.localdomain> (raw)
In-Reply-To: <20060824090741.J30362@mail.kroptech.com>
Ar Iau, 2006-08-24 am 09:07 -0400, ysgrifennodd Adam Kropelin:
> Jeff Garzik <jeff@garzik.org> wrote:
> with sw RAID of course if the builder is careful to use multiple PCI
> cards, etc. Sw RAID over your motherboard's onboard controllers leaves
> you vulnerable.
Generally speaking the channels on onboard ATA are independant with any
vaguely modern card. And for newer systems well the motherboard tends to
be festooned with random SATA controllers, all separate!
next prev parent reply other threads:[~2006-08-24 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 3:34 Linux: Why software RAID? Jeff Garzik
2006-08-24 4:22 ` Richard Scobie
2006-08-24 8:19 ` Jeff Garzik
2006-08-24 20:08 ` Richard Scobie
2006-08-24 5:20 ` Chris Friesen
2006-08-24 5:25 ` H. Peter Anvin
2006-08-26 20:55 ` Dan Williams
2006-08-24 5:43 ` Mattias Wadenstein
2006-08-24 13:07 ` Adam Kropelin
2006-08-24 13:20 ` Alan Cox [this message]
2006-08-24 13:36 ` Adam Kropelin
2006-08-24 13:42 ` Gordon Henderson
2006-09-04 17:29 ` Bill Davidsen
2006-08-24 14:55 ` Mark Lord
[not found] ` <44EDB843.2020608@perkel.com>
2006-08-24 15:21 ` Alan Cox
2006-09-04 17:31 ` Bill Davidsen
2006-09-04 17:31 ` Joel Jaeggli
-- strict thread matches above, loose matches on Subject: below --
2006-08-26 3:50 linux
2006-08-26 12:18 ` Raz Ben-Jehuda(caro)
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=1156425650.3007.140.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akropel1@rochester.rr.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=marc@perkel.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 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).