Skip to contentSkip to conversation

Problem with reiserfs 3.5.34 under 2.2.19

DISCUSSION Stephan von Krawczynski 2 participants 2 messages Oct 6, 2001 – Oct 8, 2001

lore
Share & tools
lore
#0 lore raw

Hello,

I had some serious crash today originated by a reiserfs 3.5.32 on 2.2.19 which panic'd telling me something with inodes is wrong. Unfortunately the msg was only to see on the screen and I didn't write it down. So I decided to update to 3.5.34 and give it a try, again. Now I see the following during normal operation:

Oct  6 12:14:05 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965
0
 0] and key in entry [3 68965 0 0] do not match
Oct  6 12:14:18 heather last message repeated 25 times
Oct  6 12:14:19 heather kernel: vs-13048: reiserfs_iget: key in inode [0 13612
0
 0] and key in entry [13609 13612 0 0] do not match
Oct  6 12:14:21 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965
0
 0] and key in entry [3 68965 0 0] do not match
Oct  6 12:14:48 heather last message repeated 55 times
Oct  6 12:15:29 heather last message repeated 14 times
Oct  6 12:16:29 heather last message repeated 8 times
Oct  6 12:17:42 heather last message repeated 5 times
Oct  6 12:18:19 heather kernel: vs-13048: reiserfs_iget: key in inode [0 13612
0
 0] and key in entry [13609 13612 0 0] do not match
Oct  6 12:18:29 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965

0
0] and key in entry [3 68965 0 0] do not match

What does this mean? What should be done? Does this fs survive, or am I to reformat?

Regards,
Stephan

#1 lore raw
Quoted 7 lines · Stephan von Krawczynski

Hello,

I had some serious crash today originated by a reiserfs 3.5.32 on 2.2.19 which panic'd telling me something with inodes is wrong. Unfortunately the msg was only to see on the screen and I didn't write it down. So I decided to update to 3.5.34 and give it a try, again. Now I see the following during normal operation:

Are you using "heather" box as NFS server (with knfsd)?

Quoted 19 lines
Oct  6 12:14:05 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965
0
 0] and key in entry [3 68965 0 0] do not match
Oct  6 12:14:18 heather last message repeated 25 times
Oct  6 12:14:19 heather kernel: vs-13048: reiserfs_iget: key in inode [0 13612
0
 0] and key in entry [13609 13612 0 0] do not match
Oct  6 12:14:21 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965
0
 0] and key in entry [3 68965 0 0] do not match
Oct  6 12:14:48 heather last message repeated 55 times
Oct  6 12:15:29 heather last message repeated 14 times
Oct  6 12:16:29 heather last message repeated 8 times
Oct  6 12:17:42 heather last message repeated 5 times
Oct  6 12:18:19 heather kernel: vs-13048: reiserfs_iget: key in inode [0 13612
0
 0] and key in entry [13609 13612 0 0] do not match
Oct  6 12:18:29 heather kernel: vs-13048: reiserfs_iget: key in inode [0 68965
Quoted 5 lines

0
0] and key in entry [3 68965 0 0] do not match

What does this mean? What should be done? Does this fs survive, or am I to reformat?

Take latest reiserfsprogs (3.x.0k-pre10) from ftp.namesys.com, compile them, run its reiserfsck --check /device and send results to Reiserfs-list (CCed in this message).

Quoted 3 lines

Regards,
Stephan

Nikita.

Quoted 1 line

-