From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: 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:37:18 +0400 [thread overview]
Message-ID: <20020925173718.A17138@namesys.com> (raw)
In-Reply-To: <200209251533.19567.Dieter.Nuetzel@hamburg.de>
Hello!
On Wed, Sep 25, 2002 at 03:33:19PM +0200, Dieter N?tzel wrote:
> > > As I said, I'm a newbie on NFS, and I've been reading quite a lot about
> > > the interactions of it with journalling file systems. Namely, last thing
> > > I remeber is I should put the journal on a different volume, if at all
> > No, this is not required for NFS (And never was).
> > There is nothing special about running NFS off reiserfs (v3.6 on-disk
> > format) filesystems. (in case of kernel nfsd, there are some difficulties
> > with userspace nfsd, so it should be avoided).
> Excuse me but this is not clear for me.
> Oleg, you told him to avoid knfsd?
No I said to avoid unfsd (I already made that clear in separate private email)
> > You may want to put your /home volume on some kind of RAID1 device to
> > increase data safeness from hardware errors and to increase access (read)
> > speed. (but this is storage space ineffective of course).
> 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.
Bye,
Oleg
next prev parent reply other threads:[~2002-09-25 13:37 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 [this message]
2002-09-25 13:46 ` Matthias Urlichs
2002-09-25 13:51 ` Oleg Drokin
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=20020925173718.A17138@namesys.com \
--to=green@namesys.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=jmarcet@pobox.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.