From: Hans-Peter Jansen <hpj@urpla.net>
To: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
linux-kernel@vger.kernel.org
Subject: Re: FileSystem XFS vs RiserFS vs ext3
Date: Mon, 17 Mar 2003 22:11:13 +0100 [thread overview]
Message-ID: <200303172211.13078.hpj@urpla.net> (raw)
In-Reply-To: <E18uq2v-0004P7-00@calista.inka.de>
On Monday 17 March 2003 09:32, Bernd Eckenfels wrote:
> NFS is a bit tricky. Reiser used to be broken on it, and at least from
> large XFS NFS Servers I know that they tend to be unstable, still.
The last big problems with NFS on big ReiserFS shares where fixed with
2.4.19 (IIRC). Since then, at least I haven't experienced any logic
induced failures in this area with my heavily used diskless setups on
up to 80 GB ReiserFS, shared with NFS. I enjoy this configuration a lot.
Bye,
Pete
next prev parent reply other threads:[~2003-03-17 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 5:01 FileSystem XFS vs RiserFS vs ext3 Alex Lau 劉俊賢
2003-03-17 8:32 ` Bernd Eckenfels
2003-03-17 21:11 ` Hans-Peter Jansen [this message]
2003-03-17 22:21 ` Bryan Whitehead
2003-03-18 2:26 ` Alex Lau 劉俊賢
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=200303172211.13078.hpj@urpla.net \
--to=hpj@urpla.net \
--cc=ecki@calista.eckenfels.6bone.ka-ip.net \
--cc=linux-kernel@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