All of lore.kernel.org
 help / color / mirror / Atom feed
From: AndyLiebman@aol.com
To: linux-raid@vger.kernel.org
Subject: Hardware versus Software
Date: Wed, 19 May 2004 02:49:44 EDT	[thread overview]
Message-ID: <ac.5847806b.2ddc5d88@aol.com> (raw)

I'm sure this has been discussed many times on the list but I was asked this 
question today and I'm not sure how to respond: 

Under Linux (i.e., a distribution such as Mandrake 10 -- with an up-to-date 
2.6 kernel), is a "true hardware RAID-5" created through a SATA card such as 
the 3ware 8506 or the new 3ware 9500 series any SAFER or MORE RELIABLE than a 
software RAID created with the same card? 

In my benchmark comparisons between software and hardware RAID, I get 
significantly better performance using "software RAID". With eight 250 GB disks, I 
get about 175 MB/sec reading and about 150 MB/sec writing when my system is 
configured as software RAID. With hardware RAID the figures drop to about 125/100 
MB/sec. 

I'm only using my machines as file servers, so they aren't busy doing any 
other tasks besides sending data packets through Gigabit Ethernet and running 
disk I/O. 

But the question still remains, is there any other safety and reliability 
advantage to using Hardware? Is the data on a Hardware RAID more likely to remain 
intact in the event of a computer crash or freeze? 

Or in the event of an abrupt power failure (I have a UPS on the system, but 
that could fail, or the power cables could be pulled out of the computer or 
somebody could accidently shut it down). All of these power failure scenarios are 
very unlikely, but they COULD occur. 

Would Hardware RAID survive better than Software? I can't see why, but maybe 
I'm missing something. 

In my situation where the server isn't running any other software, the only 
advantage I can see to hardware RAID is that rebuilding in the event of a disk 
failure is a little easier for non-experts. But I'm writing a program to 
automate the software RAID rebuilding process so that non-experts can do it 
themselves. 

Your informed comments would be appreciated. 

Andy Liebman

             reply	other threads:[~2004-05-19  6:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  6:49 AndyLiebman [this message]
2004-05-19 19:00 ` Hardware versus Software Ricky Beam
2004-05-19 20:03   ` Ming Zhang
2004-05-19 22:02     ` Ricky Beam
2004-05-19 23:23       ` Ming Zhang
2004-05-19 22:30 ` Ben Edwards
2004-05-21 15:57   ` Ricky Beam
2004-05-20  2:00 ` dean gaudet
  -- strict thread matches above, loose matches on Subject: below --
2004-05-21 17:44 Salyzyn, Mark
2004-05-21 18:39 ` Guy
2004-05-21 18: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=ac.5847806b.2ddc5d88@aol.com \
    --to=andyliebman@aol.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 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.