From: Neil Brown <neilb@suse.de>
To: Norman Elton <normelton@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid over 48 disks
Date: Wed, 19 Dec 2007 07:28:20 +1100 [thread overview]
Message-ID: <18280.11620.381726.737353@notabene.brown> (raw)
In-Reply-To: message from Norman Elton on Tuesday December 18
On Tuesday December 18, normelton@gmail.com wrote:
> We're investigating the possibility of running Linux (RHEL) on top of
> Sun's X4500 Thumper box:
>
> http://www.sun.com/servers/x64/x4500/
>
> Basically, it's a server with 48 SATA hard drives. No hardware RAID.
> It's designed for Sun's ZFS filesystem.
>
> So... we're curious how Linux will handle such a beast. Has anyone run
> MD software RAID over so many disks? Then piled LVM/ext3 on top of
> that? Any suggestions?
>
> Are we crazy to think this is even possible?
Certainly possible.
The default metadata is limited to 28 devices, but with
--metadata=1
you can easily use all 48 drives or more in the one array. I'm not
sure if you would want to though.
If you just wanted an enormous scratch space and were happy to lose
all your data on a drive failure, then you could make a raid0 across
all the drives which should work perfectly and give you lots of
space. But that probably isn't what you want.
I wouldn't create a raid5 or raid6 on all 48 devices.
RAID5 only survives a single device failure and with that many
devices, the chance of a second failure before you recover becomes
appreciable.
RAID6 would be much more reliable, but probably much slower. RAID6
always needs to read or write every block in a stripe (i.e. it always
uses reconstruct-write to generate the P and Q blocks, It never does
a read-modify-write like raid5 does). This means that every write
touches every device so you have less possibility for parallelism
among your many drives.
It might be instructive to try it out though.
RAID10 would be a good option if you are happy wit 24 drives worth of
space. I would probably choose a largish chunk size (256K) and use
the 'offset' layout.
Alternately, 8 6drive RAID5s or 6 8raid RAID6s, and use RAID0 to
combine them together. This would give you adequate reliability and
performance and still a large amount of storage space.
Have fun!!!
NeilBrown
next prev parent reply other threads:[~2007-12-18 20:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 17:29 Raid over 48 disks Norman Elton
2007-12-18 18:27 ` Justin Piszcz
2007-12-18 19:34 ` Thiemo Nagel
2007-12-18 19:52 ` Norman Elton
2007-12-18 20:19 ` Thiemo Nagel
2007-12-18 20:25 ` Justin Piszcz
2007-12-18 21:13 ` Thiemo Nagel
2007-12-18 21:20 ` Jon Nelson
2007-12-18 21:40 ` Thiemo Nagel
2007-12-18 21:43 ` Justin Piszcz
2007-12-18 21:21 ` Justin Piszcz
2007-12-19 15:21 ` Bill Davidsen
2007-12-19 15:02 ` Justin Piszcz
2007-12-20 16:48 ` Thiemo Nagel
2007-12-21 1:53 ` Bill Davidsen
2007-12-18 18:45 ` Robin Hill
2007-12-18 20:28 ` Neil Brown [this message]
2007-12-19 8:27 ` Mattias Wadenstein
2007-12-19 15:26 ` Bill Davidsen
2007-12-21 11:03 ` Leif Nixon
2007-12-25 17:31 ` pg_mh, Peter Grandi
2007-12-25 21:08 ` Bill Davidsen
2007-12-18 20:36 ` Brendan Conoboy
2007-12-18 23:50 ` Guy Watkins
2007-12-18 23:58 ` Justin Piszcz
2007-12-18 23:59 ` Justin Piszcz
2007-12-19 12:08 ` Russell Smith
2007-12-21 10:57 ` Leif Nixon
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=18280.11620.381726.737353@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=normelton@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).