Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: AndyLiebman@aol.com, linux-raid@vger.kernel.org
Subject: Re: Hardware versus Software
Date: Wed, 19 May 2004 16:03:02 -0400	[thread overview]
Message-ID: <1084996982.4948.198.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.33.0405191452450.14297-100000@sweetums.bluetronic.net>

On Wed, 2004-05-19 at 15:00, Ricky Beam wrote:
> On Wed, 19 May 2004 AndyLiebman@aol.com wrote:
> >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?
> 
> The linux software RAID is good stuff.  It *can* be difficult to repair
> an array in a few cases -- don't put the root FS in a non-mirrored array
> and they shouldn't be a problem.
> 
> As you don't care about CPU cycles used by the array, you're far better
> off using the software raid with normal drive controllers. (esp. true
> for SATA.)  Hardware RAID cards generally offer better managability
> and stability -- the OS doesn't have to know if a drive fails, they're
> designed to hot-swap drives with little or no fuss, etc.  But, they will
> be just a reliable as anything else.
is there any support from linux that can do this hot swappable a little
easier? 


> 
> For a system I never want to have to touch, I use hardware raid.  For those
> systems sitting at my feet, that isn't as important.
> 
> --Ricky
> 
> 
> -
> 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
-- 
 --------------------------------------------------
| Ming Zhang, PhD. Student
| Dept. of Electrical & Computer Engineering
| College of Engineering
| University of Rhode Island
| Kingston RI. 02881
| e-mail: mingz at ele.uri.edu
| Tel. (401) 874-2293 
| Fax. (401) 782-6422
| http://www.ele.uri.edu/~mingz/
 --------------------------------------------------




  reply	other threads:[~2004-05-19 20:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  6:49 Hardware versus Software AndyLiebman
2004-05-19 19:00 ` Ricky Beam
2004-05-19 20:03   ` Ming Zhang [this message]
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=1084996982.4948.198.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=AndyLiebman@aol.com \
    --cc=jfbeam@bluetronic.net \
    --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