From: Chris Cox <chris_cox@stercomm.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] EXT3 vs Reiserfs
Date: Mon Dec 8 10:19:02 2003 [thread overview]
Message-ID: <3FD4A42E.3070609@stercomm.com> (raw)
In-Reply-To: <CEADF0D83077F7458B763904E47AA709287BA7@exchange.neokimia.com>
Yanick Quirion wrote:
> Hi all,
>
> Could you please tell what is the best filesystem for linux between ext3 and reiserfs?
>
> I know that ext3 can handle ACLs and not online fs extend, and reiserfs do not seems to support ACLs (I found some patches for kernel 2.4.21, but there are errors when I apply them to the kernel sources), but can be extend while it's online.
>
> I'm just asking for your personal opinion and knowledge with them.
>
If you are using SUSE, then use reiserfs. It has ACLs and is mostly patched.
If you are using RH, then use ext3. RH in the past has been known to have
a broken reiserfs (not known for keeping it patched).
In my performance benchmarks, I found reiserfs to be somewhere between jfs and ext3, where
ext3 was the fastest, but reiserfs doing exceptionally well on random file creates
and deletes. Thought ext3 beats reiserfs in many of our tests, it was not by
an overwhelming margin. We were very surprised by the lack of performance of JFS.. though
it did have the lowest CPU utilization of the 3.
We run SUSE primarily... therefore we use reiserfs (mostly with LVMs).
RH is sorta new to the LVM thing... so although we use ext3 on our RH systems,
most of them do not use LVM. We have over 7TB of data that uses LVM with
reiserfs... we're quite pleased with the performance and capability.
We love the ability to do resize_reiserfs while the filesystem is mounted.
Constantly amazes the "Unix" purists.
next prev parent reply other threads:[~2003-12-08 10:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 8:41 [linux-lvm] EXT3 vs Reiserfs Yanick Quirion
2003-12-08 9:02 ` Jose Luis Domingo Lopez
2003-12-08 9:09 ` Markus Schiltknecht
2003-12-08 9:32 ` Matt
2003-12-08 9:50 ` Markus Schiltknecht
2003-12-08 9:59 ` Matt
2003-12-08 10:14 ` Markus Schiltknecht
2003-12-08 10:16 ` Spam
2003-12-08 10:19 ` Chris Cox [this message]
2003-12-08 10:25 ` Spam
2003-12-08 10:36 ` Markus Baertschi
2003-12-08 11:20 ` Chris Cox
2003-12-09 11:53 ` Remco Post
2003-12-09 12:30 ` Chris Cox
2003-12-08 10:30 ` Markus Baertschi
2003-12-10 7:58 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 9:16 Little, Chris
2003-12-08 9:44 ` Markus Schiltknecht
2003-12-08 13:56 ` Ajay Shekhawat
2003-12-08 14:06 ` Spam
2003-12-08 14:09 ` Mike Williams
2003-12-08 9:51 Little, Chris
2003-12-08 15:22 Yanick Quirion
2003-12-08 22:52 ` Ajay Shekhawat
2003-12-09 14:36 Little, Chris
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=3FD4A42E.3070609@stercomm.com \
--to=chris_cox@stercomm.com \
--cc=linux-lvm@sistina.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.