From: "Michael" <michael@insulin-pumpers.org>
To: linux-raid@vger.kernel.org
Subject: Re: How safe is software RAID compared to how safe hardware RAID
Date: Tue, 18 Nov 2003 15:48:55 -0800 [thread overview]
Message-ID: <200311182348.hAINmo204434@bzs.org> (raw)
In-Reply-To: <PPEOJEIEFLAONFNHJPOOAEICGOAA.jim@jimtreats.com>
> Hi folks..
>
> hopefully everything will be working soon and i can get on with
> trying to get some backup scripts working :)
>
> I am going to stick with this software RAID for the near future if
> it carries on working correctly.. I was just wondering what peoples
> views were of software vs hardware raid... anything and everything
> really.. I'm not that up on all the technology... I know that 3ware
> have a good rep in hardware... I also imagine that for more exotic
> RAID configurations its obviously a help to not stress the CPU with
> the RAID tasks.. for me tho with simple mirroring the CPU costs are
> minimal.. the linux core is a sturdy base to build upon so is
> software raid in this way a perfectly acceptible reliable RAID
> solution..
>
Your choice is to use "hardware" raid which is really just software
raid implemented with a little bitty processor and some firmware, or
"software" raid which is open source and runs on your honken'
big-fast (relatively speaking) main processor. For i86 this means
that the raid parity calculations are carried out by the mmi unit
which sits idle most of the time anyway. It would be tough to
actually find the missing cpu cycles. I've not done the benchmarks,
but others on the list claim that software raid is faster than any of
the hardware implimentations. My experience with several raid cards
leads me to believe that software raid is far more robust.
Michael
running linux software raid since 1996
next prev parent reply other threads:[~2003-11-18 23:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 19:24 recommended sata controllers? Mark Hahn
2003-11-18 19:33 ` Andrew Hogue
2003-11-18 20:12 ` HELP.. how to remove a spare drive i accidently added James R Bamford
2003-11-18 22:38 ` Neil Brown
2003-11-18 23:12 ` How safe is software RAID compared to how safe hardware RAID is!? James R Bamford
2003-11-18 23:34 ` Neil Brown
2003-11-18 23:51 ` Franc Carter
2003-11-19 0:04 ` James R Bamford
2003-11-19 0:23 ` 3tcdgwg3
2003-11-21 14:59 ` Eric Wood
2003-11-20 20:53 ` Tomi Orava
2003-11-20 23:38 ` Neil Brown
2003-11-18 23:39 ` Kourosh
2003-11-18 23:44 ` Frank Smith
2003-11-18 23:48 ` Michael [this message]
2003-11-19 7:56 ` Luca Berra
2003-11-19 16:55 ` Bill Rugolsky Jr.
2003-11-28 6:04 ` HighPoint 1820 (8pt sata pcix, $170) Mark Hahn
2003-11-28 6:13 ` jlewis
2003-11-28 15:18 ` How to change RAID1 to NON_RAID (lilo problem) Mehrdad Ziaei
2003-11-28 19:47 ` HighPoint 1820 (8pt sata pcix, $170) Jeff Garzik
2003-11-19 20:19 ` How safe is software RAID compared to how safe hardware RAID Kanoa Withington
2003-11-19 22:28 ` Gordon Henderson
2003-11-21 14:02 ` How safe is software RAID compared to how safe hardware RAID is!? Rechenberg, Andrew
2003-11-21 14:24 ` Lars Marowsky-Bree
2003-11-18 22:05 ` Is my raid setup speed ok?! James R Bamford
2003-11-19 4:09 ` Guy
2003-11-19 13:56 ` James R Bamford
2003-11-19 16:49 ` Guy
2003-11-19 17:06 ` Matthew Mitchell
2003-11-19 19:52 ` Guy
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=200311182348.hAINmo204434@bzs.org \
--to=michael@insulin-pumpers.org \
--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).