All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Heinz-Josef Claes <hjclaes@web.de>
Cc: reiserfs-list@namesys.com, Chris Mason <mason@suse.com>
Subject: Re: How to build a big file server
Date: Thu, 05 Jun 2003 14:05:41 +0400	[thread overview]
Message-ID: <3EDF15F5.2020908@namesys.com> (raw)
In-Reply-To: <1054800852.1997.15.camel@wusel.schnulli.de>

Heinz-Josef Claes wrote:

>Hi,
>
>I did't found information about my problem on namesys, so I try to ask
>here.
>
>I plan to build a big fileserver for Deutscher Bundestag (German
>Parliament) who is converting to linux on the server side. In the
>beginning it will be used in a testing environment and later multiple of
>them in production use.
>
>Here are some questions:
>
>- 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)?
>
>- At this time, we plan to use reiserfs. What are the advantages /
>disadvantages of using the raid 1 for journaling for the (big) raid 5
>(performance, recovery)? The system will be heavily used with
>storebackup (www.sf.net/projects/storebackup) witch means that lots of
>hard links have to be created as fast as possible.
>
>- BTW: I'm using a ZIP drive on the parallel port with reiserfs. Does it
>make sense to put the journal for the ZIP drive on the hard disk of the
>laptop?
>
>Thanks for taking your time,
>Heinz-Josef Claes
>
>
>
>
>  
>
Do you plan to do synchronous work loads involving lots of little 
fsyncs?  The RAID 5 will not perform well for that purpose, otherwise it 
should work well even for the journal.  Chris will correct me if I err.

-- 
Hans



  parent reply	other threads:[~2003-06-05 10:05 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 ` Hans Reiser [this message]
2003-06-05 10:24   ` How to build a big file server 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
     [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=3EDF15F5.2020908@namesys.com \
    --to=reiser@namesys.com \
    --cc=hjclaes@web.de \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.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.