LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Problem with reiserfs 3.5.34 under 2.2.19
Date: Mon, 8 Oct 2001 12:04:13 +0400	[thread overview]
Message-ID: <15297.24061.128383.739430@beta.reiserfs.com> (raw)
In-Reply-To: <20011006122640.271536fe.skraw@ithnet.com>
In-Reply-To: <20011006122640.271536fe.skraw@ithnet.com>

Stephan von Krawczynski writes:
 > 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)?

 > 
 > 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?

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).

 > 
 > Regards,
 > Stephan

Nikita.

 > -

      reply	other threads:[~2001-10-08  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06 10:26 Stephan von Krawczynski
2001-10-08  8:04 ` Nikita Danilov [this message]

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=15297.24061.128383.739430@beta.reiserfs.com \
    --to=nikita@namesys.com \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.com \
    --subject='Re: Problem with reiserfs 3.5.34 under 2.2.19' \
    /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

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).