All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Matthias Urlichs <smurf@noris.de>
Cc: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>,
	Javier Marcet <jmarcet@pobox.com>,
	reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: NFS setup for a reiserfs-based /home
Date: Wed, 25 Sep 2002 17:51:28 +0400	[thread overview]
Message-ID: <20020925175128.A3477@namesys.com> (raw)
In-Reply-To: <20020925154626.S32363@noris.de>

Hello!

On Wed, Sep 25, 2002 at 03:46:27PM +0200, Matthias Urlichs wrote:

> > > I'll suggest RAID5 (4 or more disks plus 1 or more spare) for all your 
> > > storage.
> > RAID5 is CPU hungry on writes, also writes are slower compared to RAID1.
> ... on the other hand, you need fewer disks than with RAID1.  ;-)

On the third hand, in RAID1 setup with N disks I won't mind failure of
N-1 disks. ;)

> Anyway, reasonably fast hardware RAID controllers do exist, so this isn't
> necessarily a problem.

This is just matter of truest, if you trust the binary closed source firmware
from such a device, that it will handle failures and this kind of stuff
correctly, go for it.
With Linux' softraid paranoid people can verify their own worst assumptions by
just reading source code ;)

Bye,
    Oleg

  reply	other threads:[~2002-09-25 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 21:57 NFS setup for a reiserfs-based /home Javier Marcet
2002-09-25  7:40 ` Oleg Drokin
2002-09-25 13:33   ` Dieter Nützel
2002-09-25 13:37     ` Oleg Drokin
2002-09-25 13:46       ` Matthias Urlichs
2002-09-25 13:51         ` Oleg Drokin [this message]
2002-09-25 14:09           ` Matthias Urlichs
2002-09-25 14:24             ` Oleg Drokin
2002-09-25 18:25             ` Hans Reiser
     [not found]               ` <3D920F90.7060206@edsons.demon.nl>
2002-09-25 20:37                 ` Hans Reiser
2002-09-25 15:48           ` bscott

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=20020925175128.A3477@namesys.com \
    --to=green@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=jmarcet@pobox.com \
    --cc=reiserfs-list@namesys.com \
    --cc=smurf@noris.de \
    /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.