From: Steffen Grunewald <steffen@gfz-potsdam.de>
To: linux-kernel@vger.kernel.org
Subject: Re: reiserfs error message
Date: Fri, 13 Jul 2001 18:26:01 +0200 [thread overview]
Message-ID: <20010713182600.B29470@dss19> (raw)
In-Reply-To: <20010712133544.R10669@dss19> <630460000.995033868@tiny>
In-Reply-To: <630460000.995033868@tiny>; from mason@suse.com on Fri, Jul 13, 2001 at 10:17:49AM -0400
On Fri 2001-07-13 (10:17), Chris Mason wrote:
>
>
> 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.
Unfortunately I now have to guess which FS is affected.
I'll look for an upgrade from SuSE.
> The only known way to trigger this problems involves running an older version
> of reiserfsck --rebuild-tree. Have you done that?
No. But perhaps the system did it when I changed from 7.0 to 7.1?
Steffen
--
Steffen Grunewald | GFZ | PB 2.2 | Telegrafenberg E3 | D-14473 Potsdam
» email: steffen(at)gfz-potsdam.de | fax/fon: +49-331-288-1266/-1245 «
Success is a journey, not a destination. So stop running.
--- www.despair.com
prev parent reply other threads:[~2001-07-13 16:26 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
2001-07-13 16:26 ` Steffen Grunewald [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=20010713182600.B29470@dss19 \
--to=steffen@gfz-potsdam.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.