All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Baertschi" <markus@markus.org>
To: "linux-lvm@sistina.com" <linux-lvm@sistina.com>
Subject: Re: [linux-lvm] EXT3 vs Reiserfs
Date: Mon Dec  8 10:30:03 2003	[thread overview]
Message-ID: <E1ATOFw-0003wR-7w@server6.hostpoint.ch> (raw)
In-Reply-To: <CEADF0D83077F7458B763904E47AA709287BA7@exchange.neokimia.com>

Yanick,

If you are looking for a stable filesystem and are not really worried
about performance I'd stick with ext3. If necessary you can get a kernel
patch to allow for online resizing.

If you have many small files and need the performance then reiser is an
option. I'm worried about data integrity with Reiser. Once in a while
a stories about lost files with Reiser pops up. I'll be more confident
when all these stories are a couple of years old. Loosing data is the one
thing I don't forgive a filesystem.

There is an extensive report on filesystem performance on
         http://fsbench.netnation.com/

Markus

On Mon, 8 Dec 2003 09:39:38 -0500, 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.

>Thanks.

>Regards,

>-----------
>Yanick Quirion
>Administrateur Réseau/Network Manager
>NEOKIMIA INC.
>Institut de Pharmacologie de Sherbrooke
>3e étage (Édifice Z5)
>3001 12e avenue Nord
>Sherbrooke, Québec
>CANADA
>J1H 5N4
> 
>Tél.:    +1 819 820-6040
>Direct:  +1 819 820-6855
>Fax.:    +1 819 820-6841
> 
>email: Yanick.Quirion@neokimia.com


>_______________________________________________
>linux-lvm mailing list
>linux-lvm@sistina.com
>http://lists.sistina.com/mailman/listinfo/linux-lvm
>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/




--
  Markus Baertschi             Phone: ++41 (21) 807 1677
  Bas du Rossé 14b             Fax  : ++41 (21) 807 1678
  CH-1163, Etoy                Email: markus@markus.org
  Switzerland                  Homepage: www.markus.org

  parent reply	other threads:[~2003-12-08 10:30 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
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 [this message]
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=E1ATOFw-0003wR-7w@server6.hostpoint.ch \
    --to=markus@markus.org \
    --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.