From: Oleg Drokin <green@namesys.com>
To: Vadim <vadim_t@teleline.es>
Cc: reiserfs mailing list <reiserfs-list@namesys.com>
Subject: Re: vs-5150: search_by_key: invalid format found in block 30690. Fsck?
Date: Mon, 18 Aug 2003 10:08:52 +0400 [thread overview]
Message-ID: <20030818060852.GB16183@namesys.com> (raw)
In-Reply-To: <200308151939.03324.vadim_t@teleline.es>
Hello!
On Fri, Aug 15, 2003 at 07:39:02PM +0200, Vadim wrote:
> I just noticed quite a lot of those:
> vs-5150: search_by_key: invalid format found in block 9170. Fsck?
> vs-13070: reiserfs_read_inode2: i/o failure occurred trying to
> find stat data of [3614 3618 0x0 SD]
> is_tree_node: node level 65448 does not match to the expected one
> 1
> vs-5150: search_by_key: invalid format found in block 14568.
> Fsck?
Some of the blocks are got filled with garbage for some (unknown) reason.
> The disk seems to be good, no errors, kernel is 2.4.21 with LVM
> 1.0.7.
> Why does this error happen? Is it a bug fixed in a later version?
Well, I am not sure there is a bug.
What was happenning before you started to get those messsages? Were there any
unexpected shutdowns and you do not have write cache disabled in your harddrives
or something like that?
> BTW, it'd be nice if it told me what partition it happened on.
We merged a patch that does just this in 2.4.22-pre3
Bye,
Oleg
next prev parent reply other threads:[~2003-08-18 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 17:39 vs-5150: search_by_key: invalid format found in block 30690. Fsck? Vadim
2003-08-18 6:08 ` Oleg Drokin [this message]
2003-08-18 8:00 ` Vadim
2003-08-18 13:35 ` Oleg Drokin
2003-08-18 17:28 ` Vadim
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=20030818060852.GB16183@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vadim_t@teleline.es \
/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.