From: Jon Hardcastle <jd_hardcastle@yahoo.com>
To: Raz <raziebe@gmail.com>, Bill Davidsen <davidsen@tmr.com>
Cc: linux-fsdevel@vger.kernel.org,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
linux-xfs@oss.sgi.com, linux-aio@kvack.org
Subject: Re: How to configure 36 disks ?
Date: Mon, 23 Mar 2009 09:02:14 -0700 (PDT) [thread overview]
Message-ID: <174852.24274.qm@web51309.mail.re2.yahoo.com> (raw)
In-Reply-To: <49C7AC2C.9090307@tmr.com>
I'd like to understand how you even go attaching that many devices to a system.. I am 'comparatively' new to this.. and have a 6 raid5 system.. not enterprise.. and i have slammed into case/power/sat slot issues already. What sort of hardware must one use to grow to a 36 array system!
-----------------------
N: Jon Hardcastle
E: Jon@eHardcastle.com
'..Be fearful when others are greedy, and be greedy when others are fearful.'
-----------------------
--- On Mon, 23/3/09, Bill Davidsen <davidsen@tmr.com> wrote:
> From: Bill Davidsen <davidsen@tmr.com>
> Subject: Re: How to configure 36 disks ?
> To: "Raz" <raziebe@gmail.com>
> Cc: 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>
> Date: Monday, 23 March, 2009, 3:35 PM
> Raz wrote:
> > 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.
> >
> >
> ___ snip ___
>
> > Any other ideas ?
>
> Yes, you have the whole solution rotated 90 degrees.
> Consider your original solution #2 below... You have no
> redundancy if one whole DAS box fails, which is certainly a
> possible failure mode. If you put the RAID0 horizontally,
> two arrays size six in each DAS, then RAID6 vertically, if
> one DAS fails completely you still have a functioning
> system, and the failure results for individual drives
> remains about the same, while the rebuild time will be
> longer.
>
> 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 |
>
>
> In addition, you can expand this configuration by adding
> more DAS units. This addresses several of your goals.
>
> In practice, just to get faster rebuild as the array gets
> larger, I suspect you would find it was worth making the
> horizontal arrays RAID5 instead of RAID0, just to minimize
> time to full performance.
>
> -- bill davidsen <davidsen@tmr.com>
> CTO TMR Associates, Inc
>
> "You are disgraced professional losers. And by the
> way, give us our money back."
> - Representative Earl Pomeroy, Democrat of North Dakota
> on the A.I.G. executives who were paid bonuses after a
> federal bailout.
>
>
> --
> 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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-03-23 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:59 How to configure 36 disks ? Raz
2009-03-23 13:59 ` Raz
2009-03-23 14:12 ` Emmanuel Florac
2009-03-23 16:32 ` Raz
2009-03-23 15:35 ` Bill Davidsen
2009-03-23 15:35 ` Bill Davidsen
2009-03-23 16:02 ` Jon Hardcastle [this message]
2009-03-23 16:22 ` Mark Lord
2009-03-23 16:22 ` Mark Lord
2009-03-23 16:23 ` Christopher Smith
2009-03-23 16:23 ` Christopher Smith
2009-03-23 16:28 ` Raz
2009-03-23 16:28 ` Raz
2009-03-23 16:45 ` Greg Freemyer
2009-03-23 16:45 ` Greg Freemyer
2009-03-23 18:32 ` Mikael Abrahamsson
2009-03-23 18:32 ` Mikael Abrahamsson
2009-03-23 16:52 ` Raz
2009-03-23 18:33 ` Richard Scobie
2009-03-24 19:38 ` Goswin von Brederlow
2009-03-24 19:38 ` Goswin von Brederlow
2009-03-25 12:14 ` Drew
-- strict thread matches above, loose matches on Subject: below --
2009-03-27 8:31 Michael Monnerie
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=174852.24274.qm@web51309.mail.re2.yahoo.com \
--to=jd_hardcastle@yahoo.com \
--cc=Jon@eHardcastle.com \
--cc=davidsen@tmr.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 \
--cc=raziebe@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.