From: Christian Mayrhuber <christian.mayrhuber@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Furure of ReiserfsV3?
Date: Wed, 29 Oct 2003 15:31:28 +0100 [thread overview]
Message-ID: <3F9FCF40.8060807@gmx.net> (raw)
In-Reply-To: <1067436839.1632.253.camel@tiny.suse.com>
Chris Mason wrote:
> On Wed, 2003-10-29 at 09:02, Christian Mayrhuber wrote:
>
>>Hi,
>>
>>if someone looks at the feature matrix of the major filesystems in
>>kernel 2.6.0 it tells you the following:
>>
>>FS data ordered EA ACL Quota sec. labels ext. journal
>>======================================================================
>>ext2 N Y Y Y Y N
>>ext3 Y Y Y Y Y Y
>>xfs N N Y Y N Y
>>jfs N N Y ? N Y
>>reiserfs N N N Y N Y
>>(reiserfs) Y* Y** Y** Y N Y
>>
>>* data logging patches by Chris Mason (SuSE)
>>** EA/ACL patches by Jeff Mahoney (SuSE)
>>
>>The current feature situation does not look great for reiserfs.
>> From my point of view the latest data logging patches seem to behave
>>very solid and are desireable to have in 2.6.x.
>>I have no experience with the EA/ACL patches from Jeff Mahoney, but
>>SuSE uses them for a long time.
>>
>>What can be expected to be seen in reiserfs V3 before reiser4's big
>>time? Or has reiserfs V3 entered a hard feature freeze.
>
>
> SuSE is actively porting all of this. Even though I've been saying this
> for over a year now, it really is happening ;-) Basically as we migrate
> to 2.6 for our products, we'll be pulling in all the features we added
> during the 2.4 kernels.
>
> v3 has a lot of users, so we've no intention of leaving them behind in
> the 2.6 series kernels.
>
> -chris
>
>
Short summary of Hans and Chris Mason:
FS data ordered EA ACL Quota sec. labels ext. journal
======================================================================
reiserfs Y N N Y N Y
reiserfs_suse Y Y Y Y N Y
which is, IMHO, pretty good.
Great work developers!
--
lg, Chris
next prev parent reply other threads:[~2003-10-29 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 14:02 Furure of ReiserfsV3? Christian Mayrhuber
2003-10-29 14:12 ` Hans Reiser
2003-10-29 14:14 ` Chris Mason
2003-10-29 14:31 ` Christian Mayrhuber [this message]
2003-10-28 23:07 ` Thomas Graham
[not found] ` <.192.168.0.99.1067382465.squirrel@sml.dyndns.org>
2003-10-29 15:44 ` Christian Mayrhuber
[not found] ` <.202.66.40.14.1067446837.squirrel@sml.dyndns.org>
[not found] ` <3FA10515.4080403@gmx.net>
2003-10-30 11:03 ` Thomas Graham
[not found] ` <.147.8.44.10.1067511800.squirrel@sml.dyndns.org>
2003-11-02 19:07 ` Mike Fedyk
2003-10-29 16:31 ` Soeren Sonnenburg
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=3F9FCF40.8060807@gmx.net \
--to=christian.mayrhuber@gmx.net \
--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.