Forked reiserfsprogs

Forked reiserfsprogs

[Edward Shishkin]

This is a recap of current situation with reiserfsprogs (from my
standpoint):

          -- 3.6.19.1
        /
3.6.19    ---- 3.6.20 --- 3.6.20.1

Descriptions:

Reiserfsprogs-3.6.19
Status: stable
Comments: This is a standard package which is used in most distros
with the ReiserFS support.

Reiserfsprogs-3.6.20
Status: stable
Comments: This contains massive cleanups and an --rebuild-tree
optimization (made by Vitaly Fertman) for specific filesystem
corruption which made reiserfsck to work extremely slow (including
the fixup for a problem which caused reiserfsck to consume to 100%
of CPU on phase 2).

Reiserfsprogs-3.6.19.1
Status: stable
Comments: This contains changes made by Jeff Mahoney (everything
got testing as a part of latest SuSE distros).

Reiserfsprogs-3.6.20.1
Status: beta???
Comments: This contains the work about improving of overall
reiserfsck performance. This work was done by Vladimir Saveliev
for EMC. NOTE: despite Vladimir forked 3.6.19, I consider it as
an update of 3.6.20 (because his improvements includes the fixups
from 3.6.20).

I am about to put the forked stuff above for wide public needs
(at kernel.org). All brunches are supposed to be merged at 3.6.21
after Vladimir's branch gets more testing.

Problems:

1. The status of Reiserfsprogs-3.6.20.1 should be clarified.
   Did the Vladimir's branch get testing?
2. I don't have Reiserfsprogs-3.6.20.1. Are there any snapshot
   on this mirror that can be put for public needs:
   ftp://ftp.icm.edu.pl/packages/linux-reiserfs ?
3. Perhaps, I will need help in addressing possible bugreports
   and the final merge of all branches.

Any comments, updates, suggestions?

Thanks,
Edward.

Re: Forked reiserfsprogs

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward Shishkin wrote:
> This is a recap of current situation with reiserfsprogs (from my
> standpoint):
> 
>          -- 3.6.19.1
>        /
> 3.6.19    ---- 3.6.20 --- 3.6.20.1
> 
> Descriptions:
> 
> Reiserfsprogs-3.6.19
> Status: stable
> Comments: This is a standard package which is used in most distros
> with the ReiserFS support.
> 
> Reiserfsprogs-3.6.20
> Status: stable
> Comments: This contains massive cleanups and an --rebuild-tree
> optimization (made by Vitaly Fertman) for specific filesystem
> corruption which made reiserfsck to work extremely slow (including
> the fixup for a problem which caused reiserfsck to consume to 100%
> of CPU on phase 2).
> 
> Reiserfsprogs-3.6.19.1
> Status: stable
> Comments: This contains changes made by Jeff Mahoney (everything
> got testing as a part of latest SuSE distros).
> 
> Reiserfsprogs-3.6.20.1
> Status: beta???
> Comments: This contains the work about improving of overall
> reiserfsck performance. This work was done by Vladimir Saveliev
> for EMC. NOTE: despite Vladimir forked 3.6.19, I consider it as
> an update of 3.6.20 (because his improvements includes the fixups
> from 3.6.20).
> 
> I am about to put the forked stuff above for wide public needs
> (at kernel.org). All brunches are supposed to be merged at 3.6.21
> after Vladimir's branch gets more testing.
> 
> Problems:
> 
> 1. The status of Reiserfsprogs-3.6.20.1 should be clarified.
>   Did the Vladimir's branch get testing?

I believe this is the version I was working with. It got testing, and
the results weren't good. I'm not sure if these are specific to
Vladimir's version or to Vitaly's version, but when I pushed it for a
SLE10 SP2 alpha, I ended up getting lots of bug reports. They focused
mainly in the area of endianness and divide-by-zero errors. So, I
wouldn't call this version stable at all. I didn't have the time or
interest to figure out what these problems were especially since, at the
time, I was told a real 3.6.20 didn't actually exist. I ended up backing
out the change and porting all my patches to what you're calling 3.6.19.1.

> 2. I don't have Reiserfsprogs-3.6.20.1. Are there any snapshot
>   on this mirror that can be put for public needs:
>   ftp://ftp.icm.edu.pl/packages/linux-reiserfs ?
> 3. Perhaps, I will need help in addressing possible bugreports
>   and the final merge of all branches.
> 
> Any comments, updates, suggestions?

If we actually have a stable 3.6.20, I'd be happy to forward port my
patches. One thing needs to happen, though: We absolutely need to start
testing on big endian hardware. We ship reiserfs on both powerpc and
s390, and hit the endian bugs quickly on those systems.

Btw, thanks for all getting the space on kernel.org!

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFIDAchLPWxlyuTD7IRAie0AKCoOnXWWKwkqtUew3pb1LOUTIrdJACdEe+X
uV9LfXfU79yQKzyu9XvN1ZQ=
=joDB
-----END PGP SIGNATURE-----

Re: Forked reiserfsprogs

[Edward Shishkin]

Jeff Mahoney wrote:

> Edward Shishkin wrote:

[...]

> >Problems:
>
> >1. The status of Reiserfsprogs-3.6.20.1 should be clarified.
> >  Did the Vladimir's branch get testing?
>
>
> I believe this is the version I was working with. It got testing, and
> the results weren't good. I'm not sure if these are specific to
> Vladimir's version or to Vitaly's version,


I think it was Vitaly's one (3.6.20), as Vladimir told about monthly
snapshots somewhere in ./tmp..

> but when I pushed it for a
> SLE10 SP2 alpha, I ended up getting lots of bug reports. They focused
> mainly in the area of endianness and divide-by-zero errors. So, I
> wouldn't call this version stable at all.


Hum.. I didn't know about it. It seems we need to rename it to something
like 3.6.20-preX..

> I didn't have the time or
> interest to figure out what these problems were especially since, at the
> time, I was told a real 3.6.20 didn't actually exist. I ended up backing
> out the change and porting all my patches to what you're calling 3.6.19.1.
>
> >2. I don't have Reiserfsprogs-3.6.20.1. Are there any snapshot
> >  on this mirror that can be put for public needs:
> >  ftp://ftp.icm.edu.pl/packages/linux-reiserfs ?
> >3. Perhaps, I will need help in addressing possible bugreports
> >  and the final merge of all branches.
>
> >Any comments, updates, suggestions?
>
>
> If we actually have a stable 3.6.20, I'd be happy to forward port my
> patches. One thing needs to happen, though: We absolutely need to start
> testing on big endian hardware. We ship reiserfs on both powerpc and
> s390, and hit the endian bugs quickly on those systems.
>

Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for 
reiser4),
but s390 seems to be exotic here..

Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.

Thanks Jeff.

Re: Forked reiserfsprogs

[Jeff Mahoney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edward Shishkin wrote:
> Jeff Mahoney wrote:
>> If we actually have a stable 3.6.20, I'd be happy to forward port my
>> patches. One thing needs to happen, though: We absolutely need to start
>> testing on big endian hardware. We ship reiserfs on both powerpc and
>> s390, and hit the endian bugs quickly on those systems.
>>
> 
> Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for
> reiser4),
> but s390 seems to be exotic here..

That'll be fine. You don't need to test on all platforms. A ppc64 would
probably be better, but a G3 will work.

> Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.

Sounds good.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFIDnOyLPWxlyuTD7IRAsnSAJ4nvWjZQirBhoaz/9kQ/blalomMPgCfTrEU
OIpqVfvIKZYx7kjZm2+lhds=
=8dSb
-----END PGP SIGNATURE-----

Re: Forked reiserfsprogs

[Jake Maciejewski]

On Wed, 2008-04-23 at 01:28 +0400, Edward Shishkin wrote:
> Jeff Mahoney wrote:
> 
> > Edward Shishkin wrote:
> 
> [...]
> 
> > >Problems:
> >
> > >1. The status of Reiserfsprogs-3.6.20.1 should be clarified.
> > >  Did the Vladimir's branch get testing?
> >
> >
> > I believe this is the version I was working with. It got testing, and
> > the results weren't good. I'm not sure if these are specific to
> > Vladimir's version or to Vitaly's version,
> 
> 
> I think it was Vitaly's one (3.6.20), as Vladimir told about monthly
> snapshots somewhere in ./tmp..
> 
> > but when I pushed it for a
> > SLE10 SP2 alpha, I ended up getting lots of bug reports. They focused
> > mainly in the area of endianness and divide-by-zero errors. So, I
> > wouldn't call this version stable at all.
> 
> 
> Hum.. I didn't know about it. It seems we need to rename it to something
> like 3.6.20-preX..
> 
> > I didn't have the time or
> > interest to figure out what these problems were especially since, at the
> > time, I was told a real 3.6.20 didn't actually exist. I ended up backing
> > out the change and porting all my patches to what you're calling 3.6.19.1.
> >
> > >2. I don't have Reiserfsprogs-3.6.20.1. Are there any snapshot
> > >  on this mirror that can be put for public needs:
> > >  ftp://ftp.icm.edu.pl/packages/linux-reiserfs ?
> > >3. Perhaps, I will need help in addressing possible bugreports
> > >  and the final merge of all branches.
> >
> > >Any comments, updates, suggestions?
> >
> >
> > If we actually have a stable 3.6.20, I'd be happy to forward port my
> > patches. One thing needs to happen, though: We absolutely need to start
> > testing on big endian hardware. We ship reiserfs on both powerpc and
> > s390, and hit the endian bugs quickly on those systems.
> >
> 
> Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for 
> reiser4),

You could also try PearPC. On a fast x86/amd64 machine it probably isn't
any slower than a low-spec G3.

I have a beige G3 I'm not doing anything with (aside from testing
reiser4 on it some time ago), but getting it to boot Linux without MacOS
8/9 installed is borderline voodoo, so I assume you wouldn't be
interested.

> but s390 seems to be exotic here..
> 
> Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.
> 
> Thanks Jeff.
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Jake Maciejewski <maciejej@msoe.edu>

Re: Forked reiserfsprogs

[Edward Shishkin]

Jake Maciejewski wrote:

>On Wed, 2008-04-23 at 01:28 +0400, Edward Shishkin wrote:
>  
>
>>Jeff Mahoney wrote:
>>
>>    
>>
[...]

>>>If we actually have a stable 3.6.20, I'd be happy to forward port my
>>>patches. One thing needs to happen, though: We absolutely need to start
>>>testing on big endian hardware. We ship reiserfs on both powerpc and
>>>s390, and hit the endian bugs quickly on those systems.
>>>
>>>      
>>>
>>Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for 
>>reiser4),
>>    
>>
>
>You could also try PearPC. On a fast x86/amd64 machine it probably isn't
>any slower than a low-spec G3.
>
>I have a beige G3 I'm not doing anything with (aside from testing
>reiser4 on it some time ago)
>

did reiser4 work?

>, but getting it to boot Linux without MacOS
>8/9 installed is borderline voodoo, so I assume you wouldn't be
>interested.
>
>  
>
>>but s390 seems to be exotic here..
>>
>>Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.
>>
>>Thanks Jeff.
>>--
>>To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>    
>>

Re: Forked reiserfsprogs

[Jake Maciejewski]

On Fri, 2008-04-25 at 22:45 +0400, Edward Shishkin wrote:
> Jake Maciejewski wrote:
> 
> >On Wed, 2008-04-23 at 01:28 +0400, Edward Shishkin wrote:
> >  
> >
> >>Jeff Mahoney wrote:
> >>
> >>    
> >>
> [...]
> 
> >>>If we actually have a stable 3.6.20, I'd be happy to forward port my
> >>>patches. One thing needs to happen, though: We absolutely need to start
> >>>testing on big endian hardware. We ship reiserfs on both powerpc and
> >>>s390, and hit the endian bugs quickly on those systems.
> >>>
> >>>      
> >>>
> >>Perhaps, I'll buy a cheap Mac G3 for testing (it is also needed for 
> >>reiser4),
> >>    
> >>
> >
> >You could also try PearPC. On a fast x86/amd64 machine it probably isn't
> >any slower than a low-spec G3.
> >
> >I have a beige G3 I'm not doing anything with (aside from testing
> >reiser4 on it some time ago)
> >
> 
> did reiser4 work?

It didn't mount. I sent my results to the list, archive available at
<http://marc.info/?l=reiserfs-devel&m=112347984314050&w=2>.

> >, but getting it to boot Linux without MacOS
> >8/9 installed is borderline voodoo, so I assume you wouldn't be
> >interested.
> >
> >  
> >
> >>but s390 seems to be exotic here..
> >>
> >>Ok, I'll put what I have: 3.6.19.1 and renamed 3.6.20.
> >>
> >>Thanks Jeff.
> >>--
> >>To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> >>the body of a message to majordomo@vger.kernel.org
> >>More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>    
> >>
> 
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Jake Maciejewski <maciejej@msoe.edu>