All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vitezslav T. Se'm" <travis@inway.cz>
To: Sam Vilain <sam@vilain.net>
Cc: Heinz-Josef Claes <hjclaes@web.de>, reiserfs-list@namesys.com
Subject: Re: How to build a big file server
Date: Fri, 06 Jun 2003 13:16:35 +0200	[thread overview]
Message-ID: <3EE07813.3000104@inway.cz> (raw)
In-Reply-To: 200306060143.13516.sam@vilain.net

Hi.

Sam Vilain wrote:

 >On Thu, 05 Jun 2003 20:14, Heinz-Josef Claes wrote:
 >
 >
 >>- I plan to build a system with IDE 250GB drives. 7 of them for raid 5
 >>and one hot spare. The OS will be on separate hardware raid 1 on smaller
 >>disks. Does anybody have experience with IDE controlers for the big
 >>disks? Is it better to use hardware raid oder software raid
 >>(performance)?
 >>
 >>
 >
 >Yes, if massive disk space at virtually no cost is what you're after,
 >it has to be IDE.  But, you don't have to give up the benefits of a
 >servicable data centre.  Check out http://www.acme-technology.co.uk/
 >for some fairly snazzy hot swap IDE rack mount enclosures, cases and
 >more.  There must be other vendors out there, too.  If you've got that
 >many disks, you NEED hot swap!
 >
 >As for the software RAID vs hardware RAID, my experience is that
 >software RAID 1 can deliver the same amount of disk space as hardware
 >RAID 5 for less total cost, factoring in the price of the RAID
 >controller.  Of course, your storage density is worse for RAID 1, but
 >you could probably still fit your 10TB into a single rack, assuming
 >you can get 8 disks in a 3U chassis.  RAID 1 in any form will *always*
 >outperform RAID 5, especially in the event of a failure.  RAID 1
 >arrays hardly notice, RAID 5 arrays slow to a crawl.
 >
 >btw, I wouldn't necessarily be too worried about stacking too many
 >devices on a single chain.  Benchmark heavily all configurations with
 >a workload and close to the real workload of the device before buying
 >dozens of controllers, or settling on one plan recommended by some
 >self-professed `expert' trolling the reiserfs-list.  Your bottleneck
 >may not be where you think.
 >

This is not about performace mostly, but about reliability. When U have
2 disks on one ribon, there is a serious problem, when one of them
crash, because in 99% cases, the other disk stops responding to. This is
IDE, not SCSI.

Travis

 >I'd also strongly suggest getting a motherboard with 64 bit and/or
 >66MHz PCI bus.  The Tyan ThunderK7 is pretty good - a dual capable
 >Athlon board that's stable as hell, and you can run the OpenBIOS
 >project on it - manage your servers with a serial terminal server (eg,
 >a PC with a serial breakout card) instead of a dumbass KVM switch.
 >
 >Then, you'd have something that's almost as good as a commerical UNIX
 >platform, but not really.  Personally, I'd get a quote for the arrays
 >running on Sparc hardware from http://www.anysystem.com/ (used Sun
 >parts peddlers) and offer that as a comparison.
 >
 >Running LVM to allocate a large RAID volume works exceedingly well
 >from a system administration standpoint, especially with reiserfs.
 >It's online resizing support is second to none
 >

-- 

"Byval jsem krotitelem zvirat... Vetsinou tech nejnebezpecnejsich.
- Krotitelem zvirat?
Jo. Je to logicky pokracovani po tom, co jsem byl ucitelem... jenomze se
nemusis starat o rodice."





  parent reply	other threads:[~2003-06-06 11:16 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  8:14 How to build a big file server Heinz-Josef Claes
2003-06-05  8:25 ` Carl-Daniel Hailfinger
2003-06-05  8:55   ` Andreas Dilger
2003-06-05  9:51     ` Hendrik Visage
2003-06-05  8:33 ` Ragnar Kjørstad
2003-06-05  8:42   ` Heinz-Josef Claes
2003-06-05  8:45     ` Marc-Christian Petersen
2003-06-05  9:30       ` Heinz-Josef Claes
2003-06-05 11:27       ` Bill Rees
2003-06-10 13:28       ` myciel
2003-06-10 13:36         ` Heinz-Josef Claes
2003-06-10 14:13           ` myciel
2003-06-12 20:34             ` Lars O. Grobe
2003-06-05  8:46   ` Oleg Drokin
2003-06-05  8:50     ` Heinz-Josef Claes
2003-06-05  9:04       ` Oleg Drokin
2003-06-05  9:17         ` Heinz-Josef Claes
2003-06-05 10:29           ` Russell Coker
2003-06-05 10:45             ` Heinz-Josef Claes
2003-06-05 16:47               ` Carl-Daniel Hailfinger
2003-06-05 17:01                 ` Soeren Sonnenburg
2003-06-05 17:06                 ` Ragnar Kjørstad
2003-06-06  9:41                   ` Heinz-Josef Claes
2003-06-05 13:38           ` Hans Reiser
2003-06-05 12:06         ` Heinz-Josef Claes
2003-06-05  9:45 ` Christophe Saout
2003-06-05 10:07   ` Soeren Sonnenburg
2003-06-05  9:59 ` Russell Coker
2003-06-05 10:13   ` Heinz-Josef Claes
2003-06-05 10:25     ` Russell Coker
2003-06-05 10:38       ` Heinz-Josef Claes
2003-06-05 11:11         ` Russell Coker
2003-06-05 13:48       ` Chris Mason
2003-06-14 11:11         ` data-logging for 2.4.21+ (was Re: How to build a big file server) Manuel Krause
2003-06-05 10:05 ` How to build a big file server Hans Reiser
2003-06-05 10:24   ` Heinz-Josef Claes
2003-06-05 13:43 ` Sam Vilain
2003-06-05 13:55   ` Heinz-Josef Claes
2003-06-06 11:15   ` Vitezslav T. Se'm
2003-06-06 15:15     ` Russell Coker
2003-06-06 11:16   ` Vitezslav T. Se'm [this message]
     [not found] <no.id>
2003-06-05 23:49 ` The Amazing Dragon

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=3EE07813.3000104@inway.cz \
    --to=travis@inway.cz \
    --cc=hjclaes@web.de \
    --cc=reiserfs-list@namesys.com \
    --cc=sam@vilain.net \
    /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.