xfs
[Top] [All Lists]

Re: Everyone's favorite offtopic topic

To: Andrew Klaassen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx
Subject: Re: Everyone's favorite offtopic topic
From: Seth Mos <knuffie@xxxxxxxxx>
Date: Sun, 29 Jul 2001 12:23:36 +0200
In-reply-to: <20010728231625.C19907@dkp.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 23:16 28-7-2001 -0400, Andrew Klaassen wrote:
Hi, all.

A number of times, questions have popped up on this list about
building really large arrays of IDE disks.  Does anybody know if
there's a list dedicated to that?  If not, does anybody have
suggestions as to the best way to get something like that set
up?

I ask because I haven't really found an appropriate forum for
it; the range of issues that come up (filesystems, hardware,
RAID) cut across so many boundaries that it's difficult to keep
from going wildly offtopic no matter which list(s) one is on.
And most of the people building these arrays are venturing into
the unknown; it'd be handy to have a place to swap experience
about hardware weirdnesses and filesystem quirks and performance
notes, to inform others about successful configurations and
failures.

Anybody else think there might be enough interest to make
something like this a go?

There recently was a message about building a $5000 dollar IDE raid on slashdot IIRC.
Don't know the URL anymore.


Basic configuration was purchasing a large case which can house 16 disks
Purchase 16 100GB Maxtor IDE disks (the 540DX uses less power)
Purchase 2 3ware Escalade 6800 controllers
A PC for booting the machine.

That's about it. My home PC can house 16 3.5"x1.0" disks but it's not really a standard atx enclosure. http://www.yeongyang.com/products/yy0320-0330.htm
But you will rather soon run into powersupply problems if you use more power hungry IDE disk.
If you think about using 7200RPM disks you better start looking for multiple 400W powersupply's. IDE disks tend to have the problem to all start to spin up at boot. Scsi does this when asked to :-)


Cheers

--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.


<Prev in Thread] Current Thread [Next in Thread>