From: michael@estone.ca
To: linux-raid@vger.kernel.org
Subject: Re: Raid over 48 disks ... for real now
Date: Fri, 18 Jan 2008 08:08:49 -0800 [thread overview]
Message-ID: <20080118080849.9cidbh0so4wkkc44@estone.ca> (raw)
In-Reply-To: <6b3a7f010801170819o59533c39qf4dada60a6f8701@mail.gmail.com>
Quoting Norman Elton <normelton@gmail.com>:
> I posed the question a few weeks ago about how to best accommodate
> software RAID over an array of 48 disks (a Sun X4500 server, a.k.a.
> Thumper). I appreciate all the suggestions.
>
> Well, the hardware is here. It is indeed six Marvell 88SX6081 SATA
> controllers, each with eight 1TB drives, for a total raw storage of
> 48TB. I must admit, it's quite impressive. And loud. More information
> about the hardware is available online...
>
> http://www.sun.com/servers/x64/x4500/arch-wp.pdf
>
> It came loaded with Solaris, configured with ZFS. Things seemed to
> work fine. I did not do any benchmarks, but I can revert to that
> configuration if necessary.
>
> Now I've loaded RHEL onto the box. For a first-shot, I've created one
> RAID-5 array (+ 1 spare) on each of the controllers, then used LVM to
> create a VolGroup across the arrays.
>
> So now I'm trying to figure out what to do with this space. So far,
> I've tested mke2fs on a 1TB and a 5TB LogVol.
>
> I wish RHEL would support XFS/ZFS, but for now, I'm stuck with ext3.
> Am I better off sticking with relatively small partitions (2-5 TB), or
> should I crank up the block size and go for one big partition?
Impressive system. I'm curious to what the storage drives look like
and how they attach to the server with that many disks?
Sounds like you have some time to play around before shoving it into
production.
I wonder how long it would take to run an fsck on one large filesystem?
Cheers,
Mike
next prev parent reply other threads:[~2008-01-18 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:19 Raid over 48 disks ... for real now Norman Elton
2008-01-17 16:32 ` Norman Elton
2008-01-17 19:50 ` Janek Kozicki
2008-01-19 5:16 ` Jon Lewis
2008-01-18 16:08 ` michael [this message]
2008-01-18 17:02 ` Greg Cormier
2008-01-18 18:44 ` Norman Elton
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=20080118080849.9cidbh0so4wkkc44@estone.ca \
--to=michael@estone.ca \
--cc=linux-raid@vger.kernel.org \
/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).