http://www.namesys.com/snapshots/2004.08.09-internal.testing/

http://www.namesys.com/snapshots/2004.08.09-internal.testing/

[Vitaly Fertman]

Hello All,

This snapshot contains what was included into 2004.08.03-internal.testing

snapshot:
> updated reiser4progs-0.5.7 and the grub patch.
>
> It includes several bug fixes against the previous snapshot, and has a disk
> format change -- the layout of blocks that contain backuped fs metadata
> are changed.
>
> No kernel patch is needed for the disk format change, however fsck may
> report about some corruptions on an existent fs if a block was allocated
> for some data and has become a backup one. Fsck.reiser4 --build-fs is
> able to fix it of course, although the data in these blocks are lost then.

it also has:

- a converter from the previous format to the new one -- if you already created 
a reiser4 fs with the mkfs from some previous version of reiser4progs, first of 
all run
    $ debugfs.reiser4 -C device

- reiser4 patch for the grub-0.95

--
Thanks,
Vitaly Fertman

Re: http://www.namesys.com/snapshots/2004.08.09-internal.testing/

[Stefan Schweizer]

On grub compile:

In file included from /usr/include/aal/libaal.h:17,
                from /usr/include/reiser4/libreiser4.h:13,
                from fsys_reiser4.c:27:
/usr/include/aal/types.h:62: error: conflicting types for `va_list'
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/stdarg.h:105: error:
previous declaration of `va_list'

When I try debugfs.reiser4:

 # debugfs.reiser4 -C /dev/hda1 -f
debugfs.reiser4 1.0.0
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by 
reiser4progs/COPYING. 

Segmentation fault
 #

Obviously reiser4 likes segfaults.

Stefan

Re: http://www.namesys.com/snapshots/2004.08.09-internal.testing/

[Vitaly Fertman]

On Tuesday 10 August 2004 01:01, Stefan Schweizer wrote:
> On grub compile:
>
> In file included from /usr/include/aal/libaal.h:17,
>                 from /usr/include/reiser4/libreiser4.h:13,
>                 from fsys_reiser4.c:27:
> /usr/include/aal/types.h:62: error: conflicting types for `va_list'
> /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/include/stdarg.h:105: error:
> previous declaration of `va_list'

the test patch is sent.

> When I try debugfs.reiser4:
>
>  # debugfs.reiser4 -C /dev/hda1 -f
> debugfs.reiser4 1.0.0
> Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by
> reiser4progs/COPYING.
>
> Segmentation fault
>  #

hm, this segfault seems to happen on the initialization stage, before 
any convertion is started. looks more like some problem with building
the package itself. 
Do you have the core file? Would you send me the trace?

-- 
Thanks,
Vitaly Fertman

Re: http://www.namesys.com/snapshots/2004.08.09-internal.testing/

[Stefan Schweizer]

ok, it makes it compile, but it does not work for me:

grub> kernel (hd0,1)/
Error 17: Cannot mount selected partition

Perhabs this is related to not converting my reiser4 partition to the
new format due to the segfault.

Stefan

http://www.namesys.com/snapshots/2004.06.14-internal.testing/

[Vitaly Fertman]

Hello All, 

This snapshot includes reiser4progs-0.5.5, libaal-0.5.2 and updated 
grub patch.

It supports object plugin sets, includes improved mount entry detection 
code and many other bugfixes.

stage1_5 reiser4 support in grub does not work (and probably will not 
anymore) because reiser4_stage1_5 code does not fit 23,5K size limit, 
even when all not nessesary plugins are disabled (disable-short-keys, 
disable-X-hash, disable-X_fibre, disable-symlinks, etc) on configuring.
Use stage2 instead.

When you run fsck.reiser4 on your old reiser4 filesystem it should report 
about missed plugin set members in the root directory. fsck should be able 
to fix it running with the --fix option.

-- 
Thanks,
Vitaly Fertman

Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/

[Vitaly Fertman]

On Wednesday 04 August 2004 21:47, Hans Reiser wrote:
> Markus Törnqvist wrote:
> >On Wed, Aug 04, 2004 at 10:16:26PM +0800, Thomas Graham wrote:
> >>if a convertor are not done yet, I think we could wait until it's bundle
> >>into the .tar.gz and we could use it, actually, do we HAVE TO do that
> >>format changes ? or normal user could just ignore that except for some of
> >>them who reach problem with that ?
> >
> >I don't think you HAVE to do it, if you would, there would be a
> > compensation in the kernel, and Vitaly said there is not.
> >
> >So just avoid the reiser4progs like the plague, call the Namesys helpdesk,
> >whatever and ask Vitaly to remove the file from the web, remove the
> >code that changes the format, whatever.
> >
> >I just hope I won't hit a corruptive bug on my machine, it would be pretty
> >anticlimactic if I did and I would lose data because it decides to
> >change the format.
>
> I don't understand why Vitaly cannot do one of the things suggested on
> this thread: create an fsck option for people like Markus to use.
>
> If Vitaly does that, problem solved, yes?
>
> Chris is right that any disk format changes need to be made now.
> Vitaly, send an email defining what you propose to do, and cc the list.
> Do that now please.

I have written a converter (an option to debugfs), testing it, 
it does well for the last half an hout already. 

I am going to release another internal snapshot with the explanation 
in README how to use it.

-- 
Thanks,
Vitaly Fertman

Re: http://www.namesys.com/snapshots/2004.08.03-internal.testing/

[Hans Reiser]

Vitaly Fertman wrote:

>On Wednesday 04 August 2004 21:47, Hans Reiser wrote:
>  
>
>>Markus TЖrnqvist wrote:
>>    
>>
>>>On Wed, Aug 04, 2004 at 10:16:26PM +0800, Thomas Graham wrote:
>>>      
>>>
>>>>if a convertor are not done yet, I think we could wait until it's bundle
>>>>into the .tar.gz and we could use it, actually, do we HAVE TO do that
>>>>format changes ? or normal user could just ignore that except for some of
>>>>them who reach problem with that ?
>>>>        
>>>>
>>>I don't think you HAVE to do it, if you would, there would be a
>>>compensation in the kernel, and Vitaly said there is not.
>>>
>>>So just avoid the reiser4progs like the plague, call the Namesys helpdesk,
>>>whatever and ask Vitaly to remove the file from the web, remove the
>>>code that changes the format, whatever.
>>>
>>>I just hope I won't hit a corruptive bug on my machine, it would be pretty
>>>anticlimactic if I did and I would lose data because it decides to
>>>change the format.
>>>      
>>>
>>I don't understand why Vitaly cannot do one of the things suggested on
>>this thread: create an fsck option for people like Markus to use.
>>
>>If Vitaly does that, problem solved, yes?
>>
>>Chris is right that any disk format changes need to be made now.
>>Vitaly, send an email defining what you propose to do, and cc the list.
>>Do that now please.
>>    
>>
>
>I have written a converter (an option to debugfs), testing it, 
>it does well for the last half an hout already. 
>
>I am going to release another internal snapshot with the explanation 
>in README how to use it.
>
>  
>
good answer.

http://www.namesys.com/snapshots/2004.08.09-internal.testing/

[Vitaly Fertman]

Hello All,

This snapshot contains what was included into 2004.08.03-internal.testing 
snapshot:

> updated reiser4progs-0.5.7 and the grub patch.
> 
> It includes several bug fixes against the previous snapshot, and has a disk 
> format change -- the layout of blocks that contain backuped fs metadata 
> are changed. 
> 
> No kernel patch is needed for the disk format change, however fsck may 
> report about some corruptions on an existent fs if a block was allocated 
> for some data and has become a backup one. Fsck.reiser4 --build-fs is 
> able to fix it of course, although the data in these blocks are lost then.

and it has a converter from the previous format to the new one -- if you 
already created a reiser4 fs with the mkfs from some previous version 
of reiser4progs, first of all run 
    $ debugfs.reiser4 -C device

-- 
Thanks,
Vitaly Fertman