From: Lyle Schlueter <lyle@xkubed.com>
To: linux-raid@vger.kernel.org
Subject: Software raid - controller options
Date: Tue, 06 Nov 2007 05:20:35 +0300 [thread overview]
Message-ID: <1194315635.17361.20.camel@localhost.localdomain> (raw)
Hello,
I just started looking into software raid with linux a few weeks ago. I
am outgrowing the commercial NAS product that I bought a while back.
I've been learning as much as I can, suscribing to this mailing list,
reading man pages, experimenting with loopback devices setting up and
expanding test arrays.
I have a few questions now that I'm sure someone here will be able to
enlighten me about.
First, I want to run a 12 drive raid 6, honestly, would I be better of
going with true hardware raid like the areca ARC-1231ML vs software
raid? I would prefer software raid just for the sheer cost savings. But
what kind of processing power would it take to match or exceed a mid to
high-level hardware controller?
I haven't seen much, if any, discussion of this, but how many drives are
people putting into software arrays? And how are you going about it?
Motherboards seem to max out around 6-8 SATA ports. Do you just add SATA
controllers? Looking around on newegg (and some googling) 2-port SATA
controllers are pretty easy to find, but once you get to 4 ports the
cards all seem to include some sort of built in *raid* functionality.
Are there any 4+ port PCI-e SATA controllers cards?
Are there any specific chipsets/brands of motherboards or controller
cards that you software raid veterans prefer?
Thank you for your time and any info you are able to give me!
Lyle
next reply other threads:[~2007-11-06 2:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 2:20 Lyle Schlueter [this message]
2007-11-06 2:51 ` Software raid - controller options Richard Scobie
2007-11-06 3:20 ` Lyle Schlueter
2007-11-06 4:08 ` Richard Scobie
2007-11-06 8:16 ` Wolfgang Denk
2007-11-07 9:51 ` Goswin von Brederlow
2007-11-06 6:27 ` Wolfgang Denk
2007-11-06 6:41 ` Alberto Alonso
2007-11-06 19:27 ` Lyle Schlueter
2007-11-07 9:49 ` Goswin von Brederlow
2007-11-08 18:10 ` Bill Davidsen
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=1194315635.17361.20.camel@localhost.localdomain \
--to=lyle@xkubed.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 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).