Re: Support for ReiserFS

[Szakacsits Szabolcs]

On Fri, 1 Oct 2004, Runar Ingebrigtsen wrote:
> fre, 01.10.2004 kl. 16.11 skrev Sven Luther:
> > On Fri, Oct 01, 2004 at 08:54:00AM +0300, Yury Umanets wrote:
> > > Runar Ingebrigtsen wrote:
> > > >Is there hope for ReiserFS support in libparted anytime soon?
> > > > 
> > > It is there for few years already. You need to install progsreiserfs 
> > > first 
> > > (ftp://ftp.namesys.com/pub/libreiserfs/progsreiserfs-0.3.0.5.tar.gz) and 
> > > then build parted with reiserfs support turned on.
> > 
> > But it seems that progsreiserfs is completely unmaintained or something, at
> > least it has been kicked out of debian/sarge recently because of bugginess,
> > which forced me to remove reiserfs support in the compiled version of parted
> > in debian sarge. You can always recompile your own though if you install the
> > progsreiserfs package out of unstable though.
> 
> Very interesting. Quote http://www.namesys.com/v4/v4.html: "V3 of
> reiserfs is used as the default filesystem for SuSE, Lindows, FTOSX,
> Libranet, and Gentoo. We don't touch the V3 code except to fix a
> bug, and as a result we don't get bug reports for the current mainstream
> kernel version. It shipped before the other journaling filesystems for
> Linux, and is the most stable of them as a result of having been out the
> longest. We must caution that just as Linux 2.6 is not yet as stable as
> Linux 2.4, it will also be some substantial time before V4 is as stable
> as V3."

Explanation is in the bug-parted archive:

        http://lists.gnu.org/archive/html/bug-parted/

There are two user space reiserfs code bases, progsreiserfs and
reiserfsprogs. Parted uses the "not official" one, though this code base
is considered better and it's the official code base for Reiser4.

> What I really was wondering was when moving the start of partition in
> certain filesystems will be possible. I don't know why I didn't ask so
> in the first place.. Any news in this (the moving partition) matter?

This was also discussed several times in the list and even an easy to
implement solution was mentioned (though it's slow, it could get the 
job done until one has a lot of time to improve it for each one of
filesystems step by step performance wise).

        Szaka