From: Chris Mason <mason@suse.com>
To: Steffen Grunewald <steffen@gfz-potsdam.de>, linux-kernel@vger.kernel.org
Subject: Re: reiserfs error message
Date: Fri, 13 Jul 2001 10:17:49 -0400 [thread overview]
Message-ID: <630460000.995033868@tiny> (raw)
In-Reply-To: <20010712133544.R10669@dss19>
On Thursday, July 12, 2001 01:35:44 PM +0200 Steffen Grunewald
<steffen@gfz-potsdam.de> wrote:
> Should I worry about
>
> kernel: vs-13048: reiserfs_iget: key in inode [62743 393750 0 0] and key
> in entry [62444 393750 0 0] do not match
>
> ? This is SuSE 7.1 kernel 2.2.18, with automatic FTP updates.
>
This is due to two files sharing the same inode number, which isn't supposed
to happen. You can find the two files by doing a find -inum 393750 on the
filesystem. You probably want to grab the latest reiserfsck from
ftp.namesys.com/pub/reiserfsprogs/pre and check the entire FS.
The only known way to trigger this problems involves running an older version
of reiserfsck --rebuild-tree. Have you done that?
-chris
next prev parent reply other threads:[~2001-07-13 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 11:35 reiserfs error message Steffen Grunewald
2001-07-13 14:17 ` Chris Mason [this message]
2001-07-13 16:26 ` Steffen Grunewald
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=630460000.995033868@tiny \
--to=mason@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen@gfz-potsdam.de \
/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