From: Drew <drew.kay@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: Jon@ehardcastle.com,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
linux-aio@kvack.org, linux-xfs@oss.sgi.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Raz <raziebe@gmail.com>,
linux-fsdevel@vger.kernel.org, Bill Davidsen <davidsen@tmr.com>
Subject: Re: How to configure 36 disks ?
Date: Wed, 25 Mar 2009 05:14:42 -0700 [thread overview]
Message-ID: <c268e4660903250514y12babcc5hf42f4d3daff3fa45@mail.gmail.com> (raw)
In-Reply-To: <87hc1iemo4.fsf@frosties.localdomain>
>> 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!
>
> Well, lets see.
>
> Put 3 dual channel SAS controler in the box giving you 6 external SAS
> connectors. Buy 6 48x disk enclosures and connect them. Configure them
> all as JBOD and you get your 288 disks.
And after you've mortgaged your house, your future, and your first born ... :-P
--
Drew
"Nothing in life is to be feared. It is only to be understood."
--Marie Curie
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-03-25 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 13:59 How to configure 36 disks ? Raz
2009-03-23 14:12 ` 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 [this message]
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=c268e4660903250514y12babcc5hf42f4d3daff3fa45@mail.gmail.com \
--to=drew.kay@gmail.com \
--cc=Jon@ehardcastle.com \
--cc=davidsen@tmr.com \
--cc=goswin-v-b@web.de \
--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 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).