LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Problem with reiserfs 3.5.34 under 2.2.19
@ 2001-10-06 10:26 Stephan von Krawczynski
  2001-10-08  8:04 ` Nikita Danilov
  0 siblings, 1 reply; 2+ messages in thread
From: Stephan von Krawczynski @ 2001-10-06 10:26 UTC (permalink / raw)
  To: linux-kernel

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-10-08  8:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-06 10:26 Problem with reiserfs 3.5.34 under 2.2.19 Stephan von Krawczynski
2001-10-08  8:04 ` Nikita Danilov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).