From: Vladimir Saveliev <vs@namesys.com>
To: Hongwei Li <hwli98@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: reiserfs bug
Date: Tue, 05 Oct 2004 19:01:39 +0400 [thread overview]
Message-ID: <1096988498.10831.76.camel@tribesman.namesys.com> (raw)
In-Reply-To: <20040701060924.11587.qmail@web11202.mail.yahoo.com>
Hello
On Thu, 2004-07-01 at 10:09, Hongwei Li wrote:
> Hi:
> My machine am running linux-2.4.25, it crash in the
> reiser_panic.
> I looked at the oops and find out the followings:
> check_leaf_block_head pass the 0 as "sb" value, and
> cause reiser_panic crash.
> Any fix for this?
>
Reiserfs found metadata corruption. It is supposed to not crash but
return i/o error,
but you should reiserfsck your filesystem.
We have to improve reiserfs data corruption handling.
> static void check_leaf_block_head (struct buffer_head
> * bh)
> {
> struct block_head * blkh;
> int nr;
>
> blkh = B_BLK_HEAD (bh);
> nr = blkh_nr_item(blkh);
> if ( nr > (bh->b_size - BLKH_SIZE) / IH_SIZE)
> reiserfs_panic (0, "vs-6010:
> check_leaf_block_head: invalid item number %z", bh);
> if ( blkh_free_space(blkh) >
> bh->b_size - BLKH_SIZE - IH_SIZE * nr )
> reiserfs_panic (0, "vs-6020:
> check_leaf_block_head: invalid free space %z", bh);
>
> }
>
> void reiserfs_panic (struct super_block * sb, const
> char * fmt, ...)
> {
> show_reiserfs_locks() ;
> do_reiserfs_warning(fmt);
> printk ( KERN_EMERG "%s (device %s)\n", error_buf,
> bdevname(sb->s_dev));
> BUG ();
>
> /* this is not actually called, but makes
> reiserfs_panic() "noreturn" */
> panic ("REISERFS: panic (device %s): %s\n",
> sb ? kdevname(sb->s_dev) : "sb == 0", error_buf);
> }
>
> Li Hongwei
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-10-05 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 6:09 Hongwei Li
2004-07-01 20:44 ` Oleg Drokin
2004-10-05 15:01 ` Vladimir Saveliev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-22 23:26 Pablo Barbáchano
2005-01-23 11:13 ` Pablo Barbáchano
2002-11-28 8:28 Sönke Ruempler
2002-11-28 8:47 ` Oleg Drokin
2002-11-28 8:50 ` Sonke Ruempler
2002-11-28 8:57 ` Oleg Drokin
2002-11-28 9:04 ` Sonke Ruempler
2002-11-28 9:09 ` Oleg Drokin
2002-11-28 9:12 ` Sonke Ruempler
2002-11-28 9:13 ` Henning P. Schmiedehausen
2002-11-28 10:03 ` Oleg Drokin
2001-10-08 16:44 ReiserFS Bug Aleksander Adamowski
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=1096988498.10831.76.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=hwli98@yahoo.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
Powered by JetHome