From: Chris Cox <chris_cox@stercomm.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] EXT3 vs Reiserfs
Date: Mon Dec 8 11:20:02 2003 [thread overview]
Message-ID: <3FD4B28E.6030602@stercomm.com> (raw)
In-Reply-To: <E1ATOLU-0004dz-1c@server6.hostpoint.ch>
Markus Baertschi wrote:
> On Mon, 08 Dec 2003 10:17:50 -0600, Chris Cox wrote:
>
>>We love the ability to do resize_reiserfs while the filesystem is mounted.
>>Constantly amazes the "Unix" purists.
>
>
> This is the one feature I like most on my AIX boxes, where the stock
> LVM & JFS setup has done this for more than a decade.
>
> That a broken reiser on RH is the source of the occasiona data loss reported
> is good possibility. But that means there were broken reiser implementations
> out there of which RH assumed they were stable and they weren't.
I have never experienced the data loss element, however, since
reiser3 does not do true data journaling, but only metadata, it is
well known fact that while reiser can bring the filesystem
integrity back to normal after a bad shutdown, some data loss
is possible. This is usually true of any metadata only journaling
filesystem. Reiser4 supposed fixes this and of course has that
whiz-bang plugins feature. Could make reiser4 the best (feature wise).
I certainly have nothing against JFS or AIX. I really like its ability
to dynamically grow without intervention (though that could give
some administrators a headache).
I can't say what's going on with reiserfs and RH... again, just
because of the "stories" I've heard and occasional "ewww's" I've
personally seen with RH, I just avoid it on RH. They chose their
filesystem and that filesystem is ext3. It would be foolish
to do anything else on RH.
I have seen problems with ext3 even under RH where we would lose
entire filesystems... but anytime I mention this, I'm always
trampled on... to tell you the truth, I suspect it is an error
in ext2 even... but that opinion really offends people. I don't
use RH in general unless I have to (we're an ISV, so we support
everything). But YMMV of course!
next prev parent reply other threads:[~2003-12-08 11:20 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 [this message]
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=3FD4B28E.6030602@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.