From: Brad Campbell <brad@wasp.net.au>
To: greenjelly <big_green_jelly_Bean@yahoo.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software based SATA RAID-5 expandable arrays?
Date: Thu, 21 Jun 2007 00:52:38 +0400 [thread overview]
Message-ID: <46799396.8010800@wasp.net.au> (raw)
In-Reply-To: <11167521.post@talk.nabble.com>
greenjelly wrote:
> The options I seek are to be able to start with a 6 Drive array RAID-5
> array, then as my demand for more space increases in the future I want to be
> able to plug in more drives and incorporate them into the Array without the
> need to backup the data. Basically I need the software to add the
> drive/drives to the Array, then Rebuild the array incorporating the new
> drives while preserving the data on the original array.
I've got 2 boxes. One has 14 drives and a 480W PSU and the other has 15 drives and a 600W PSU. It's
not rocket science. Put a lot of drives in a box, make sure you have enough sata ports and power to
go around (watch your peak 12V consumption on spin up really) and use linux md. Easy.. Oh, but make
sure the drives stay cool!
For a cheap-o home server (which is what I have) I'd certainly not bother with a dedicated RAID
card. You are not even going to need GB ethernet really.. I've got 15 drives on a single PCI bus,
it's as slow as a wet week in may (in the southern hemisphere), but I'm streaming to 3 head units
which total a combined 5MB/s if I'm lucky.. Rebuilds can take up to 10 hours though.
> QUESTIONS
> Since this is a media server, and would only be used to serve Movies and
> Video to my two machines It wouldn't have to be powered up full time (My
> Music consumes less space and will be contained on two seperate machines).
> Is there a way to considerably lower the power consumption of this server
> the 90% of time its not in use?
Yes, don't poll for SMART and spin down the drives when idle (man hdparm). Use S3 sleep and WOL if
you are really clever. (I'm not, my boxes live in a dedicated server room with its own AC, but
that's because I'm nuts). I also have over 25k hours on the drives because I don't spin them down. I
figure the extra power is a trade off for drive life. They've got less than 50 spin cycles on them
in over 25k hours..
> Can Linux support Drive Arrays of Significant Sizes (4-8 terabytes)?
Yes, easily (6TB here)
> Can Linux Software support RAID-5 expandability, allowing me to increase the
> number of disks in the array, without the need to backup the media, recreate
> the array from scratch and then copy the backup to the machine (something I
> will be unable to do)?
Yes but get a cheap UPS at least (it's cheap insurance)
> I know this is a Linux forum, but I figure many of you guys work with
> Windows Server. If so does Windows 2003 provide the same support for the
> requested requirements above?
Why would you even _ask_ ??
Read the man page for mdadm, then read it again (and a third time). Then google for "Raid-5 two
drive failure linux" just to familiarise yourself with the background.
What you are doing has been done before many, many times. There are some well written sites out
there relating to building exactly what you want to build with great detail.
If you are serious about using windows, I pity you.. Linux (actually a combination of the kernel md
layer and mdadm) makes it so easy you'd be nuts to beat your head against the wall with the alternative.
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2007-06-20 20:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 22:16 Software based SATA RAID-5 expandable arrays? greenjelly
2007-06-17 22:23 ` Justin Piszcz
2007-06-18 21:14 ` Dexter Filmore
2007-06-19 8:35 ` David Greaves
2007-06-19 9:14 ` Dexter Filmore
2007-06-20 20:52 ` Brad Campbell [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 12:46 Daniel Korstad
2007-06-19 13:08 Michael
2007-06-19 13:43 Michael
2007-06-19 14:23 ` Robin Hill
2007-06-19 18:49 ` Daniel Korstad
2007-06-19 14:42 Michael
2007-06-19 21:30 ` Nix
2007-06-21 9:22 Michael
2007-06-21 20:16 ` Richard Scobie
2007-06-21 10:40 Michael
2007-06-22 15:12 jahammonds prost
2007-06-23 4:16 ` Brad Campbell
[not found] <944875.74303.qm@web54106.mail.re2.yahoo.com>
2007-07-09 19:31 ` Daniel Korstad
2007-07-11 14:21 ` Bill Davidsen
2007-07-10 21:58 jahammonds prost
2007-07-11 15:03 Daniel Korstad
2007-07-14 15:49 ` Bill Davidsen
2007-07-11 17:26 jahammonds prost
2007-07-11 19:13 ` Daniel Korstad
2007-07-11 19:26 ` Daniel Korstad
2007-07-11 20:08 Michael
2007-07-11 23:29 ` Nix
2007-07-11 20:12 jahammonds prost
2007-07-12 22:42 Michael
2007-07-13 3:54 ` Bill Davidsen
2007-07-13 15:22 ` Daniel Korstad
2007-07-13 16:48 Michael
2007-07-13 18:18 ` Bill Davidsen
2007-07-13 18:23 ` Daniel Korstad
[not found] <1914474980.1184590115562.JavaMail.root@gateway.korstad.net>
2007-07-16 14:23 ` Daniel Korstad
2007-07-16 17:34 Michael
2007-07-16 19:29 ` Daniel Korstad
2007-08-01 16:46 Michael
2007-08-01 17:13 ` David Greaves
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=46799396.8010800@wasp.net.au \
--to=brad@wasp.net.au \
--cc=big_green_jelly_Bean@yahoo.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).