From: Raz <raziebe@gmail.com>
To: linux-fsdevel@vger.kernel.org,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
linux-xfs@oss.sgi.com, linux-aio@kvack.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: How to configure 36 disks ?
Date: Mon, 23 Mar 2009 15:59:47 +0200 [thread overview]
Message-ID: <5d96567b0903230659t734677a3pb4fd77cccb54008b@mail.gmail.com> (raw)
Hello
I need to configure 3xDAS'es, each with 12 disks.
All three DAS'es are connected to a single machine.
I have the following requirements (in this order of importance)
from the storage:
1. redundancy.
having two disks failing in one raid5 breaks the entire raid. when
you have 30TB storage
it is a disaster.
2. performance.
My code eliminates Linux raid5/6 write penalty. I managed to do by
manipulating xfs and patching linux raid5 a bit.
3. modularity ( a "grow" and it will be nice to have "shrink" )
file system and volume must be able to grow. shrinking is possible
by unifying multiple file systems
under unionfs or aufs.
4. Utilize storage size.
I assume each disk is 1TB.
Solution #1
raid0
DAS1: raid5: D,D,D,D,D,D |
raid5: D,D,D,D,D,D |
|
DAS2: raid5: D,D,D,D,D,D | xfs
raid5: D,D,D,D,D,D |
|
DAS3: raid5: D,D,D,D,D,D |
raid5: D,D,D,D,D,D |
1. redundancy. no. if a single raid fails, 30 TB fails.
2. performance. good.
3. modularity. no. raid0 does not grow.
4. Size. 30TB.
Solution #2
raid0
DAS1: raid6: D,D,D,D,D,D |
raid6: D,D,D,D,D,D |
|
DAS2: raid6: D,D,D,D,D,D | xfs.
raid6: D,D,D,D,D,D |
|
DAS3: raid6: D,D,D,D,D,D |
raid6: D,D,D,D,D,D |
1. redundancy. fair. less likely three disks will break in a single raid.
2. performance. good.
3. modularity. no. raid0 does not grow.
4. size. 24 TB
Solution #3
unionfs/aufs
DAS1: raid5: D,D,D,D,D,D xfs |
raid5: D,D,D,D,D,D xfs |
|
DAS2: raid5: D,D,D,D,D,D xfs |
raid5: D,D,D,D,D,D xfs |
|
DAS3: raid5: D,D,D,D,D,D xfs |
raid5: D,D,D,D,D,D xfs |
1. redundancy. fair. if a single raid fails, only this raid fails.
2. performance. fair.
unionfs is not mainline and does not support write balancing.
aufs is not mature enough.
3. modularity. yes. grow and shrinks.
4. Size. 30TB.
Solution #4
xfs over Linux LVM
DAS1: raid6: D,D,D,D,D,D |
raid6: D,D,D,D,D,D |
|
DAS2: raid6: D,D,D,D,D,D |
raid6: D,D,D,D,D,D |
|
DAS3: raid6: D,D,D,D,D,D |
raid6: D,D,D,D,D,D |
1. redundancy. fair. less likely three disks will break in a single raid
2. performance. bad.
3. modularity. yes. grows
4. Size 24TB
Any other ideas ?
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2009-03-23 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:59 Raz [this message]
2009-03-23 14:12 ` How to configure 36 disks ? Emmanuel Florac
2009-03-23 15:35 ` Bill Davidsen
2009-03-23 16:02 ` Jon Hardcastle
2009-03-23 16:22 ` Mark Lord
2009-03-23 16:23 ` Christopher Smith
2009-03-23 16:28 ` Raz
2009-03-23 16:45 ` Greg Freemyer
2009-03-23 18:32 ` Mikael Abrahamsson
2009-03-24 19:38 ` Goswin von Brederlow
2009-03-25 12:14 ` Drew
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=5d96567b0903230659t734677a3pb4fd77cccb54008b@mail.gmail.com \
--to=raziebe@gmail.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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).