linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Christian Pernegger <pernegger@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Ok to go ahead with this setup?
Date: Thu, 22 Jun 2006 23:25:13 -0400	[thread overview]
Message-ID: <449B5F19.4070707@tmr.com> (raw)
In-Reply-To: <bb145bd20606221008p131d4daem289a6b9300757c66@mail.gmail.com>

Christian Pernegger wrote:

> Hi list!
>
> Having experienced firsthand the pain that hardware RAID controllers
> can be -- my 3ware 7500-8 died and it took me a week to find even a
> 7508-8 -- I would like to switch to kernel software RAID.
>
> Here's a tentative setup:
>
> Intel SE7230NH1-E mainboard
> Pentium D 930
> 2x1GB Crucial 533 DDR2 ECC
> Intel SC5295-E enclosure
>
> Promise Ultra133 TX2 (2ch PATA)
>   - 2x Maxtor 6B300R0 (300GB, DiamondMax 10) in RAID1
>
> Onboard Intel ICH7R (4ch SATA)
>   - 4x Western Digital WD5000YS (500GB, Caviar RE2) in RAID5
>
> * Does this hardware work flawlessly with Linux?
>
> * Is it advisable to boot from the mirror?
>  Would the box still boot with only one of the disks?


Let me say this about firmware mirror: while virtually every BIOS will 
boot the "next" disk if the first fails, some will not fail over if the 
first drive is returning a parity but still returning data. Take that 
data any way you want, drive failure at power cycle is somewhat more 
likely than failure while running.

>
> * Can I use EVMS as a frontend?
>  Does it even use md or is EVMS's RAID something else entirely?
>
> * Should I use the 300s as a single mirror, or span multiple ones over
> the two disks?
>
> * Am I even correct in assuming that I could stick an array in another
> box and have it work?
>
> Comments welcome
>
> Thanks,
>
> Chris
> -
> 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
>


-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2006-06-23  3:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 17:08 Ok to go ahead with this setup? Christian Pernegger
2006-06-22 18:04 ` Molle Bestefich
2006-06-22 18:38   ` H. Peter Anvin
2006-06-22 19:50   ` Christian Pernegger
2006-06-22 22:11     ` Molle Bestefich
2006-06-23  2:44       ` H. Peter Anvin
2006-06-23  3:27       ` Bill Davidsen
2006-06-23  6:45       ` Ricky Beam
2006-06-28  2:42       ` Mike Dresser
2006-06-28  6:23         ` bart
2006-06-28  6:45           ` Brad Campbell
2006-06-28 10:18           ` Justin Piszcz
2006-06-28 15:23             ` Mike Dresser
2006-06-28  7:25         ` Christian Pernegger
2006-06-28  7:58           ` bart
2006-06-28  8:19           ` Drive issues in RAID vs. not-RAID Gordon Henderson
2006-06-29  3:51             ` Neil Brown
2006-06-23  3:25 ` Bill Davidsen [this message]
2006-06-28 12:02 ` Ok to go ahead with this setup? Christian Pernegger

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=449B5F19.4070707@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pernegger@gmail.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).