fsck.reiser4 segfaults

fsck.reiser4 segfaults

[Sarath Menon]

Hello,

I've been using reiser4 for more than a year without any problems. The
filesystem performance has been commendable to say the least.
Yesterday, I had to powercycle my pc (due to a dma hang with my cd
drive - happens occasionaly) and after the reboot, grub would not
load. I use a single root partition (/boot inclusive) and the patched
grub sources.

I've tried booting into knoppix and compiling reiser4progs and running an fsck.

This is what I get -:
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4.
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0x3a4f3c7b
blocks:         2443880
free blocks:    428490
root block:     743745
tail policy:    0x2 (smart)
next oid:       0xf63a06
file count:     469920
tree height:    5
key policy:     LARGE


CHECKING STORAGE TREE
FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
which is in the tree already.
The whole subtree is skipped.
Segmentation fault

debugfs.reiser4 also segfaults, and a mount also fails, it complians
of a duplicate key. (I can't post the exact message because the second
livecd doesn't have X or any mail client :(


Cheers,
Sarath

--
I presume, when you pronounce iptables, you say that you are peeing tables

Re: fsck.reiser4 segfaults

[Vladimir V. Saveliev]

Hello

On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> Hello,
> 
> I've been using reiser4 for more than a year without any problems. The
> filesystem performance has been commendable to say the least.
> Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> drive - happens occasionaly) and after the reboot, grub would not
> load. I use a single root partition (/boot inclusive) and the patched
> grub sources.
> 
> I've tried booting into knoppix and compiling reiser4progs and running an fsck.
> 
what is reiser4progs's version?

> This is what I get -:
> Master super block (16):
> magic:          ReIsEr4
> blksize:        4096
> format:         0x0 (format40)
> label:          <none>
> 
> Format super block (17):
> plugin:         format40
> description:    Disk-format for reiser4.
> magic:          ReIsEr40FoRmAt
> flushes:        0
> mkfs id:        0x3a4f3c7b
> blocks:         2443880
> free blocks:    428490
> root block:     743745
> tail policy:    0x2 (smart)
> next oid:       0xf63a06
> file count:     469920
> tree height:    5
> key policy:     LARGE
> 
> 
> CHECKING STORAGE TREE
> FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> which is in the tree already.
> The whole subtree is skipped.
> Segmentation fault
> 
> debugfs.reiser4 also segfaults, and a mount also fails, it complians
> of a duplicate key. (I can't post the exact message because the second
> livecd doesn't have X or any mail client :(
> 
> 
> Cheers,
> Sarath
> 
> --
> I presume, when you pronounce iptables, you say that you are peeing tables
> 

Re: fsck.reiser4 segfaults

[Vladimir V. Saveliev]

Hello

On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> Hello,
> 
> I've been using reiser4 for more than a year without any problems. The
> filesystem performance has been commendable to say the least.
> Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> drive - happens occasionaly) and after the reboot, grub would not
> load. I use a single root partition (/boot inclusive) and the patched
> grub sources.
> 
> I've tried booting into knoppix and compiling reiser4progs and running an fsck.
> 
> This is what I get -:
> Master super block (16):
> magic:          ReIsEr4
> blksize:        4096
> format:         0x0 (format40)
> label:          <none>
> 
> Format super block (17):
> plugin:         format40
> description:    Disk-format for reiser4.
> magic:          ReIsEr40FoRmAt
> flushes:        0
> mkfs id:        0x3a4f3c7b
> blocks:         2443880
> free blocks:    428490
> root block:     743745
> tail policy:    0x2 (smart)
> next oid:       0xf63a06
> file count:     469920
> tree height:    5
> key policy:     LARGE
> 
> 
> CHECKING STORAGE TREE
> FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> which is in the tree already.
> The whole subtree is skipped.
> Segmentation fault
> 

can you please run dmesg after that and send its output?

> debugfs.reiser4 also segfaults, and a mount also fails, it complians
> of a duplicate key. (I can't post the exact message because the second
> livecd doesn't have X or any mail client :(
> 
> 
> Cheers,
> Sarath
> 
> --
> I presume, when you pronounce iptables, you say that you are peeing tables
> 

Re: fsck.reiser4 segfaults

[Sarath Menon]

reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
output tommorow - I need to get a livecd with reiser4 patches - its
more difficult than I initially thought ;)

Here's the gdb bt output - that's the max that I can provide today.

Program received signal SIGSEGV, Segmentation fault.
0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4/lib
(gdb) bt
#0  0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4
#1  0x40015959 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
#2  0x40015938 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
#3  0x40052356 in repair_filter_traverse () from /tmp/reiser4/lib/li
#4  0x40051c8c in repair_filter () from /tmp/reiser4/lib/librepair-1
#5  0x400575ea in repair_check () from /tmp/reiser4/lib/librepair-1.
#6  0x0804a1cb in main ()
#7  0x4102eda6 in __libc_start_main () from /lib/libc.so.6

I'll post the dmesg output tommorow.

Thanks,
Sarath

On 3/31/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> Hello
>
> On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> > Hello,
> >
> > I've been using reiser4 for more than a year without any problems. The
> > filesystem performance has been commendable to say the least.
> > Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> > drive - happens occasionaly) and after the reboot, grub would not
> > load. I use a single root partition (/boot inclusive) and the patched
> > grub sources.
> >
> > I've tried booting into knoppix and compiling reiser4progs and running an
> fsck.
> >
> > This is what I get -:
> > Master super block (16):
> > magic:          ReIsEr4
> > blksize:        4096
> > format:         0x0 (format40)
> > label:          <none>
> >
> > Format super block (17):
> > plugin:         format40
> > description:    Disk-format for reiser4.
> > magic:          ReIsEr40FoRmAt
> > flushes:        0
> > mkfs id:        0x3a4f3c7b
> > blocks:         2443880
> > free blocks:    428490
> > root block:     743745
> > tail policy:    0x2 (smart)
> > next oid:       0xf63a06
> > file count:     469920
> > tree height:    5
> > key policy:     LARGE
> >
> >
> > CHECKING STORAGE TREE
> > FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> > which is in the tree already.
> > The whole subtree is skipped.
> > Segmentation fault
> >
>
> can you please run dmesg after that and send its output?
>
> > debugfs.reiser4 also segfaults, and a mount also fails, it complians
> > of a duplicate key. (I can't post the exact message because the second
> > livecd doesn't have X or any mail client :(
> >
> >
> > Cheers,
> > Sarath
> >
> > --
> > I presume, when you pronounce iptables, you say that you are peeing tables
> >
>
>


--
--------------------------
I presume, when you pronounce iptables, you say that you are peeing tables

Re: fsck.reiser4 segfaults

[Michael Weissenbacher]

Hi,
> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> output tommorow - I need to get a livecd with reiser4 patches - its
> more difficult than I initially thought ;)
I'm using RIPLinux, which has reiser4 support.
http://www.tux.org/pub/people/kent-robotti/looplinux/rip/

kind regards,
Michael
-- 
/============================================================\
|       Michael Weissenbacher <webmaster@dermichi.com>       |
|                  http://www.dermichi.com/                  |
| In 2010, M$ Windows will be a quantum processing emulation |
| layer for a 128-bit mod of a 64-bit hack of a 32-bit patch |
| to a 16-bit GUI for an 8-bit operating system written for  |
| a 4-bit processor from a 2-bit company that can't stand 1  |
| bit of competition.                                        |
\============================================================/

Re: fsck.reiser4 segfaults

[Joachim Feise]

Michael Weissenbacher wrote on 03/31/06 12:21:

> Hi,
>> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
>> output tommorow - I need to get a livecd with reiser4 patches - its
>> more difficult than I initially thought ;)
> I'm using RIPLinux, which has reiser4 support.
> http://www.tux.org/pub/people/kent-robotti/looplinux/rip/


Thanks for that info. I was looking for a boot disk with reiser4 for some time.

-Joe

Re: fsck.reiser4 segfaults

[Sarath Menon]

Me too, ;) I also found http://www.lxnaydesign.net/, useful if you
need a browser to be around too.

Here's the dmesg output when i try to mount it.

reiser4[mount(11756)]: renew_sibling_link
(fs/reiser4/tree_walk.c:441)[nikita-3532]:
WARNING: Sibling nodes on the different levels: 4 != 4

reiser4[mount(11756)]: key_warning (fs/reiser4/plugin/object.c:97)[nikita-717]:
WARNING: Error for inode 42 (-5)

The kernel version seems to be a bit old at 2.6.10-lxnay3. Should I
try with a newer kernel, with debug args maybe?

Thanks,
Sarath

On 4/1/06, Joachim Feise <jfeise@gmail.com> wrote:
> Michael Weissenbacher wrote on 03/31/06 12:21:
>
> > Hi,
> >> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> >> output tommorow - I need to get a livecd with reiser4 patches - its
> >> more difficult than I initially thought ;)
> > I'm using RIPLinux, which has reiser4 support.
> > http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
>
>
> Thanks for that info. I was looking for a boot disk with reiser4 for some time.
>
> -Joe
>


--
--------------------------
I presume, when you pronounce iptables, you say that you are peeing tables

Re: fsck.reiser4 segfaults

[Jake Maciejewski]

On Sat, 2006-04-01 at 08:13 +0000, Sarath Menon wrote:
> Me too, ;) I also found http://www.lxnaydesign.net/, useful if you
> need a browser to be around too.
> 
> Here's the dmesg output when i try to mount it.
> 
> reiser4[mount(11756)]: renew_sibling_link
> (fs/reiser4/tree_walk.c:441)[nikita-3532]:
> WARNING: Sibling nodes on the different levels: 4 != 4
> 
> reiser4[mount(11756)]: key_warning (fs/reiser4/plugin/object.c:97)[nikita-717]:
> WARNING: Error for inode 42 (-5)
> 
> The kernel version seems to be a bit old at 2.6.10-lxnay3. Should I
> try with a newer kernel, with debug args maybe?

lxnay may have backported a more recent patch, but there was a plugin
set change (see http://www.mail-archive.com/reiserfs-list@namesys.com/
msg18602.html) in 2.6.11-5 such that older kernels would be unable to
mount filesystems that had been mounted with newer kernels.

> Thanks,
> Sarath
> 
> On 4/1/06, Joachim Feise <jfeise@gmail.com> wrote:
> > Michael Weissenbacher wrote on 03/31/06 12:21:
> >
> > > Hi,
> > >> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> > >> output tommorow - I need to get a livecd with reiser4 patches - its
> > >> more difficult than I initially thought ;)
> > > I'm using RIPLinux, which has reiser4 support.
> > > http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
> >
> >
> > Thanks for that info. I was looking for a boot disk with reiser4 for some time.
> >
> > -Joe
> >
> 
> 
> --
> --------------------------
> I presume, when you pronounce iptables, you say that you are peeing tables
-- 
Jake Maciejewski <maciejej@msoe.edu>

Re: fsck.reiser4 segfaults

[Vladimir V. Saveliev]

Hello

On Fri, 2006-03-31 at 20:21 +0200, Sarath Menon wrote:
> reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> output tommorow - I need to get a livecd with reiser4 patches - its
> more difficult than I initially thought ;)
> 
> Here's the gdb bt output - that's the max that I can provide today.
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4/lib
> (gdb) bt
> #0  0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4
> #1  0x40015959 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> #2  0x40015938 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> #3  0x40052356 in repair_filter_traverse () from /tmp/reiser4/lib/li
> #4  0x40051c8c in repair_filter () from /tmp/reiser4/lib/librepair-1
> #5  0x400575ea in repair_check () from /tmp/reiser4/lib/librepair-1.
> #6  0x0804a1cb in main ()
> #7  0x4102eda6 in __libc_start_main () from /lib/libc.so.6
> 
> I'll post the dmesg output tommorow.
> 

I would like to debug this problem. Can you please do
debugfs.reiser4 /dev/thatdevice -P | bzip2 -c > reiser4-metadata.bz2
and put resulting file somewhere for downloading. That should make
debugging easier.

> Thanks,
> Sarath
> 
> On 3/31/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> > Hello
> >
> > On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> > > Hello,
> > >
> > > I've been using reiser4 for more than a year without any problems. The
> > > filesystem performance has been commendable to say the least.
> > > Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> > > drive - happens occasionaly) and after the reboot, grub would not
> > > load. I use a single root partition (/boot inclusive) and the patched
> > > grub sources.
> > >
> > > I've tried booting into knoppix and compiling reiser4progs and running an
> > fsck.
> > >
> > > This is what I get -:
> > > Master super block (16):
> > > magic:          ReIsEr4
> > > blksize:        4096
> > > format:         0x0 (format40)
> > > label:          <none>
> > >
> > > Format super block (17):
> > > plugin:         format40
> > > description:    Disk-format for reiser4.
> > > magic:          ReIsEr40FoRmAt
> > > flushes:        0
> > > mkfs id:        0x3a4f3c7b
> > > blocks:         2443880
> > > free blocks:    428490
> > > root block:     743745
> > > tail policy:    0x2 (smart)
> > > next oid:       0xf63a06
> > > file count:     469920
> > > tree height:    5
> > > key policy:     LARGE
> > >
> > >
> > > CHECKING STORAGE TREE
> > > FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> > > which is in the tree already.
> > > The whole subtree is skipped.
> > > Segmentation fault
> > >
> >
> > can you please run dmesg after that and send its output?
> >
> > > debugfs.reiser4 also segfaults, and a mount also fails, it complians
> > > of a duplicate key. (I can't post the exact message because the second
> > > livecd doesn't have X or any mail client :(
> > >
> > >
> > > Cheers,
> > > Sarath
> > >
> > > --
> > > I presume, when you pronounce iptables, you say that you are peeing tables
> > >
> >
> >
> 
> 
> --
> --------------------------
> I presume, when you pronounce iptables, you say that you are peeing tables
> 

Re: fsck.reiser4 segfaults

[Sarath Menon]

CC-ing to the list.

On 4/5/06, Sarath Menon <sarathmenon@gmail.com> wrote:
> Hi Vlad,
>
> Sorry I missed your email, I wasn't really checking my mails. The dump
> is available from http://sarath.dyndns.org/r4/reiser4-metadata.bz2.
>
> Please let me know if you need more information.
>
> On 4/3/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> > Hello
> >
> > On Fri, 2006-03-31 at 20:21 +0200, Sarath Menon wrote:
> > > reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> > > output tommorow - I need to get a livecd with reiser4 patches - its
> > > more difficult than I initially thought ;)
> > >
> > > Here's the gdb bt output - that's the max that I can provide today.
> > >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > 0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4/lib
> > > (gdb) bt
> > > #0  0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4
> > > #1  0x40015959 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> > > #2  0x40015938 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> > > #3  0x40052356 in repair_filter_traverse () from /tmp/reiser4/lib/li
> > > #4  0x40051c8c in repair_filter () from /tmp/reiser4/lib/librepair-1
> > > #5  0x400575ea in repair_check () from /tmp/reiser4/lib/librepair-1.
> > > #6  0x0804a1cb in main ()
> > > #7  0x4102eda6 in __libc_start_main () from /lib/libc.so.6
> > >
> > > I'll post the dmesg output tommorow.
> > >
> >
> > I would like to debug this problem. Can you please do
> > debugfs.reiser4 /dev/thatdevice -P | bzip2 -c > reiser4-metadata.bz2
> > and put resulting file somewhere for downloading. That should make
> > debugging easier.
> >
> > > Thanks,
> > > Sarath
> > >
> > > On 3/31/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> > > > Hello
> > > >
> > > > On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> > > > > Hello,
> > > > >
> > > > > I've been using reiser4 for more than a year without any problems. The
> > > > > filesystem performance has been commendable to say the least.
> > > > > Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> > > > > drive - happens occasionaly) and after the reboot, grub would not
> > > > > load. I use a single root partition (/boot inclusive) and the patched
> > > > > grub sources.
> > > > >
> > > > > I've tried booting into knoppix and compiling reiser4progs and running an
> > > > fsck.
> > > > >
> > > > > This is what I get -:
> > > > > Master super block (16):
> > > > > magic:          ReIsEr4
> > > > > blksize:        4096
> > > > > format:         0x0 (format40)
> > > > > label:          <none>
> > > > >
> > > > > Format super block (17):
> > > > > plugin:         format40
> > > > > description:    Disk-format for reiser4.
> > > > > magic:          ReIsEr40FoRmAt
> > > > > flushes:        0
> > > > > mkfs id:        0x3a4f3c7b
> > > > > blocks:         2443880
> > > > > free blocks:    428490
> > > > > root block:     743745
> > > > > tail policy:    0x2 (smart)
> > > > > next oid:       0xf63a06
> > > > > file count:     469920
> > > > > tree height:    5
> > > > > key policy:     LARGE
> > > > >
> > > > >
> > > > > CHECKING STORAGE TREE
> > > > > FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> > > > > which is in the tree already.
> > > > > The whole subtree is skipped.
> > > > > Segmentation fault
> > > > >
> > > >
> > > > can you please run dmesg after that and send its output?
> > > >
> > > > > debugfs.reiser4 also segfaults, and a mount also fails, it complians
> > > > > of a duplicate key. (I can't post the exact message because the second
> > > > > livecd doesn't have X or any mail client :(
> > > > >
> > > > >
> > > > > Cheers,
> > > > > Sarath
> > > > >
> > > > > --
> > > > > I presume, when you pronounce iptables, you say that you are peeing tables.

Re: fsck.reiser4 segfaults

[Sarath Menon]

Hi Vlad,

This was posted a long time before. I was wondering whether the recent patches 
might have fixed this. Can you please comment? 

Thanks,
Sarath

On Monday 03 April 2006 15:51, Vladimir V. Saveliev wrote:
> Hello
>
> On Fri, 2006-03-31 at 20:21 +0200, Sarath Menon wrote:
> > reiserfsprogs and libaal are both 1.0.5. I'll give you the dmesg
> > output tommorow - I need to get a livecd with reiser4 patches - its
> > more difficult than I initially thought ;)
> >
> > Here's the gdb bt output - that's the max that I can provide today.
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4/lib
> > (gdb) bt
> > #0  0x40052dd1 in repair_filter_update_traverse () from /tmp/reiser4
> > #1  0x40015959 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> > #2  0x40015938 in reiser4_tree_trav_node () from /tmp/reiser4/lib/li
> > #3  0x40052356 in repair_filter_traverse () from /tmp/reiser4/lib/li
> > #4  0x40051c8c in repair_filter () from /tmp/reiser4/lib/librepair-1
> > #5  0x400575ea in repair_check () from /tmp/reiser4/lib/librepair-1.
> > #6  0x0804a1cb in main ()
> > #7  0x4102eda6 in __libc_start_main () from /lib/libc.so.6
> >
> > I'll post the dmesg output tommorow.
>
> I would like to debug this problem. Can you please do
> debugfs.reiser4 /dev/thatdevice -P | bzip2 -c > reiser4-metadata.bz2
> and put resulting file somewhere for downloading. That should make
> debugging easier.
>
> > Thanks,
> > Sarath
> >
> > On 3/31/06, Vladimir V. Saveliev <vs@namesys.com> wrote:
> > > Hello
> > >
> > > On Fri, 2006-03-31 at 16:21 +0200, Sarath Menon wrote:
> > > > Hello,
> > > >
> > > > I've been using reiser4 for more than a year without any problems.
> > > > The filesystem performance has been commendable to say the least.
> > > > Yesterday, I had to powercycle my pc (due to a dma hang with my cd
> > > > drive - happens occasionaly) and after the reboot, grub would not
> > > > load. I use a single root partition (/boot inclusive) and the patched
> > > > grub sources.
> > > >
> > > > I've tried booting into knoppix and compiling reiser4progs and
> > > > running an
> > >
> > > fsck.
> > >
> > > > This is what I get -:
> > > > Master super block (16):
> > > > magic:          ReIsEr4
> > > > blksize:        4096
> > > > format:         0x0 (format40)
> > > > label:          <none>
> > > >
> > > > Format super block (17):
> > > > plugin:         format40
> > > > description:    Disk-format for reiser4.
> > > > magic:          ReIsEr40FoRmAt
> > > > flushes:        0
> > > > mkfs id:        0x3a4f3c7b
> > > > blocks:         2443880
> > > > free blocks:    428490
> > > > root block:     743745
> > > > tail policy:    0x2 (smart)
> > > > next oid:       0xf63a06
> > > > file count:     469920
> > > > tree height:    5
> > > > key policy:     LARGE
> > > >
> > > >
> > > > CHECKING STORAGE TREE
> > > > FSCK: Node (743744), item (0), unit (0): Points to the block (743745)
> > > > which is in the tree already.
> > > > The whole subtree is skipped.
> > > > Segmentation fault
> > >
> > > can you please run dmesg after that and send its output?
> > >
> > > > debugfs.reiser4 also segfaults, and a mount also fails, it complians
> > > > of a duplicate key. (I can't post the exact message because the
> > > > second livecd doesn't have X or any mail client :(
> > > >
> > > >
> > > > Cheers,
> > > > Sarath
> > > >
> > > > --
> > > > I presume, when you pronounce iptables, you say that you are peeing
> > > > tables
> >
> > --
> > --------------------------
> > I presume, when you pronounce iptables, you say that you are peeing
> > tables

-- 
I don't even butter my bread.  I consider that cooking.
		-- Katherine Cebrian

fsck.reiser4 segfaults

[Jussi Suutari-Jaasko]

Hi,

I'm have a little problem with my reiser4 partition...
I can't mount it anymore and I'm unable to repair it.
I have a AMD64 platform with 64-bit Gentoo installed.

Here's the short story:

1. I was using kernel 2.6.16 with reiser4-2.6.16-4 patch
and I installed new 2.6.17 kernel with reiser4-2.6.17-3
patch. (The kernel source is Gentoo-sources since I'm using
Gentoo :)

2. After rebooting with .17 kernel I ran fsck.reiser4
on my reiser4 partion (an error was reported in the
system log earlier, saying something about keys are
inconsistent..).

3. I rebooted (again) after having to do fsck.reiser4
  --build-fs and then my system refused to boot. The
screen filled with errors telling me about inconsistent
keys etc.

4. I tried to run fsck.reiser4 through two different
reiser4-capable LiveCDs but with no luck. The fsck.reiser4
always segfaults after 2% of the whole process. First
livecd had some .17 kernel and the other .14 kernel. Both
have reiser4tools-1.0.5.

Here's the output:

--- Cut ---

# fsck.reiser4 -y /dev/hda3

*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************

Fscking the /dev/hda3 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
***** fsck.reiser4 started at Wed Aug  9 12:51:43 2006
Reiser4 fs was detected on /dev/hda3.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           409056f8-a452-469f-9847-f5777eb14de6
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format for reiser4.
magic:          ReIsEr40FoRmAt
flushes:        0
mkfs id:        0xdf9f908
blocks:         19838256
free blocks:    15095656
root block:     7366
tail policy:    0x2 (smart)
next oid:       0x815411
file count:     392526
tree height:    4
key policy:     LARGE


CHECKING STORAGE TREE
FSCK: Node (7367): The left delimiting key 
[10005:1(SD):6c696263757273:5ebbe8:0] in the parent node (7366), pos (0/4294967295)
does not match the first key [29:1(SD):0:2a:0] in the node.
FSCK: Node (7366), item (0), unit (0): Points to the node [7367] with wrong 
delimiting keys. The whole subtree is skipped.
FSCK: Node (238887), item (39), unit (0): Points to the block (7366) which 
is in the tree already. The whole subtree is skipped.
Segmentation fault

#

--- Cut ---

It does the same with all option (--fix etc).
Here's the output when I try to mount the partition:

--- Cut ---

# mount /dev/hda3 /mnt/gentoo

reiser4[mount(17242)]: traverse_tree (fs/reiser4/search.c:731)[nikita-373]:
WARNING: not found on internal node: level: 3, lock_level: 1, stop_level: 1 
lock_mode: read, bias: exact
reiser4[mount(17242)]: key_warning 
(fs/reiser4/plugin/file_plugin_common.c:514)[nikita-717]:
WARNING: Error for inode 42 (-2)
mount: No such file or directory

#

--- Cut ---

The system log says nothing. I'm a bit lost what to do.
I had some important files on that partition (and yes,
I should have done a backup). Is there a way to fix the
partition?

- Jussi

Re: fsck.reiser4 segfaults

[Jussi Suutari-Jääskö]

In addition, this was reported in the system
log after testing a little bit:

fsck.reiser4[21575]: segfault at 0000000000000008 rip 0000000000444ac5 rsp 
00007fff34eb4970 error 4

If you need more information I'll provide what
I can.

fsck.reiser4 segfaults

[Konstantin Sobolev]

Hi all,

I have 2 computers running reiser4 partitions. Once I decided to check them 
for errors, and on both machines fsck reported that SB is corrupted. I 
suppose that's because partitions were formatted by older versions of 
reiser4progs. --build-sb worked OK. Then fsck reported about some corruptions 
that were successfully repaired with --build-fs on the first machine. 
However, on the second one fsck segfaults on attempt to do a repair.

The output is:
[skip]
***** Semantic Traverse Pass: reiser4 semantic tree checking.
FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (3) set 
to (smart). Added.
FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (4) set 
to (r5_hash). Added.
FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (5) set 
to (dot_o_fibre). Added.
FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (6) set 
to (stat40). Added.
FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (7) set 
to (cde40). Added.
Segmentation fault

fsck version is fsck.reiser4 0.5.5, kernel is 2.6.4 with latest stable reiser4 
snapshot

I've packed fs metadata with debugfs.reiser4 -P /dev/hda6 | bzip2 -c > 
hda6debug.bz2, it can be downloaded from
http://www.prokhorov.org/hda6debug.bz2 , 38Mb

Partition still can be mounted but I don't know if it is risky to work with 
it, I don't want to loose it completely.
-- 
/KoS
* My other tag line is a killer!					      

Re: fsck.reiser4 segfaults

[Vitaly Fertman]

Hello,

On Thursday 15 July 2004 15:59, Konstantin Sobolev wrote:
> Hi all,
>
> I have 2 computers running reiser4 partitions. Once I decided to check them
> for errors, and on both machines fsck reported that SB is corrupted. I
> suppose that's because partitions were formatted by older versions of
> reiser4progs. --build-sb worked OK. Then fsck reported about some
> corruptions that were successfully repaired with --build-fs on the first
> machine. However, on the second one fsck segfaults on attempt to do a
> repair.
>
> The output is:
> [skip]
> ***** Semantic Traverse Pass: reiser4 semantic tree checking.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (3)
> set to (smart). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (4)
> set to (r5_hash). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (5)
> set to (dot_o_fibre). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (6)
> set to (stat40). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (7)
> set to (cde40). Added.
> Segmentation fault
>
> fsck version is fsck.reiser4 0.5.5, kernel is 2.6.4 with latest stable
> reiser4 snapshot

would you try the latest reiser4progs from 
www.namesys.com/snapshots/2004.07.13-internal.testing/

> I've packed fs metadata with debugfs.reiser4 -P /dev/hda6 | bzip2 -c >
> hda6debug.bz2, it can be downloaded from
> http://www.prokhorov.org/hda6debug.bz2 , 38Mb

if the new fsck fails we will debug it with your metadata.

> Partition still can be mounted but I don't know if it is risky to work with
> it, I don't want to loose it completely.

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 segfaults

[Konstantin Sobolev]

On Thursday 15 July 2004 16:21, Vitaly Fertman wrote:
> would you try the latest reiser4progs from
> www.namesys.com/snapshots/2004.07.13-internal.testing/

It worked OK but now I can't mount it :(

Unable to handle kernel NULL pointer dereference at virtual address 00000008
followed by registers dump and call trace

I guess my laptop is dead until new LiveCD with fresh reiser4 snapshot that 
will be able to mount it..
-- 
/KoS
* (W)indows,(I)cons,(M)ice,(P)ointers,(S)heesh!			      

Re: fsck.reiser4 segfaults

[Vitaly Fertman]

On Thursday 15 July 2004 22:45, Konstantin Sobolev wrote:
> On Thursday 15 July 2004 16:21, Vitaly Fertman wrote:
> > would you try the latest reiser4progs from
> > www.namesys.com/snapshots/2004.07.13-internal.testing/
>
> It worked OK but now I can't mount it :(

ahh, last internal releases of reiser4progs -- 0.5.5 you tried 
before and the current 0.5.6 -- should be used with the last 
autosnapshots only:
	http://www.namesys.com/auto-snapshots/
earlier reiser4 versions do not support plugin sets. After fscking
the root directory got such a pset and as a result the fs cannot be 
mounted with an old reiser4 code anymore.

> Unable to handle kernel NULL pointer dereference at virtual address
> 00000008 followed by registers dump and call trace
>
> I guess my laptop is dead until new LiveCD with fresh reiser4 snapshot that
> will be able to mount it..

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 segfaults

[Konstantin Sobolev]

On Thursday 15 July 2004 23:09, Vitaly Fertman wrote:
> On Thursday 15 July 2004 22:45, Konstantin Sobolev wrote:
> > On Thursday 15 July 2004 16:21, Vitaly Fertman wrote:
> > > would you try the latest reiser4progs from
> > > www.namesys.com/snapshots/2004.07.13-internal.testing/
> >
> > It worked OK but now I can't mount it :(
>
> ahh, last internal releases of reiser4progs -- 0.5.5 you tried
> before and the current 0.5.6 -- should be used with the last
> autosnapshots only:
> 	http://www.namesys.com/auto-snapshots/
> earlier reiser4 versions do not support plugin sets. After fscking
> the root directory got such a pset and as a result the fs cannot be
> mounted with an old reiser4 code anymore.

Yeah. Luckily I've found LiveCD with 2.6.7 sources patched with one of 
autosnapshots that successfully mounted my /usr, so now I'll be able to build 
new kernel. Can you recommend some more or less stable autosnapshot that I 
can use?

Thanks for your help :)
-- 
/KoS
* recursion n.: See Recursion
		-- The Jargon File

Re: fsck.reiser4 segfaults

[mjt]

On Thu, Jul 15, 2004 at 11:22:22PM +0400, Konstantin Sobolev wrote:
>Yeah. Luckily I've found LiveCD with 2.6.7 sources patched with one of 
>autosnapshots that successfully mounted my /usr, so now I'll be able to build 
>new kernel. Can you recommend some more or less stable autosnapshot that I 
>can use?

Seems that generally later autosnapshots are better autosnapshots.

It is recommended you turn on assertion debuggings, especially if you
don't want any faster performance than "fast enough". Just in case.

-- 
mjt

Re: fsck.reiser4 segfaults

[Vitaly Fertman]

On Thursday 15 July 2004 23:09, Vitaly Fertman wrote:
> On Thursday 15 July 2004 22:45, Konstantin Sobolev wrote:
> > On Thursday 15 July 2004 16:21, Vitaly Fertman wrote:
> > > would you try the latest reiser4progs from
> > > www.namesys.com/snapshots/2004.07.13-internal.testing/
> >
> > It worked OK but now I can't mount it :(
>
> ahh, last internal releases of reiser4progs -- 0.5.5 you tried
> before and the current 0.5.6 -- should be used with the last
> autosnapshots only:
> 	http://www.namesys.com/auto-snapshots/
> earlier reiser4 versions do not support plugin sets. After fscking
> the root directory got such a pset and as a result the fs cannot be
> mounted with an old reiser4 code anymore.

you can either build the kernel with the latest reiser4 auto-snapshot
or get reiser4progs-0.5.4. If later, fsck.reiser4-0.5.4 should be able 
to fix the root directory to the old format -- it has worked for my 
test now at least.

> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000008 followed by registers dump and call trace
> >
> > I guess my laptop is dead until new LiveCD with fresh reiser4 snapshot
> > that will be able to mount it..

-- 
Thanks,
Vitaly Fertman