From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Problem with reiserfs 3.5.34 under 2.2.19
Date: Sat, 6 Oct 2001 12:26:40 +0200 [thread overview]
Message-ID: <20011006122640.271536fe.skraw@ithnet.com> (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
next reply other threads:[~2001-10-06 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 10:26 Stephan von Krawczynski [this message]
2001-10-08 8:04 ` Problem with reiserfs 3.5.34 under 2.2.19 Nikita Danilov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011006122640.271536fe.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox