All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc)
Date: Thu, 24 Dec 2009 18:05:12 -0500	[thread overview]
Message-ID: <20091224230512.GA32757@thunk.org> (raw)
In-Reply-To: <a4423d670912241428n6917d2adsad887548612cf8ce@mail.gmail.com>

On Fri, Dec 25, 2009 at 01:28:34AM +0300, Alexander Beregalov wrote:
> 
> Kernel is 2.6.33-rc1-00366-g2f99f5c
> Ext4 mounts ext3 filesystem
> 
> kernel BUG at fs/ext4/inode.c:1063!

OK, that's this BUG which is triggering:

	if (mdb_free) {
		/* Account for allocated meta_blocks */
		mdb_claim = EXT4_I(inode)->i_allocated_meta_blocks;
		BUG_ON(mdb_free < mdb_claim);  <------- BUG triggered
		mdb_free -= mdb_claim;

Can you replicate this?  If so, I'd like to ask you to replicate with
the following debugging patch applied:

--- fs/ext4/inode.c	2009-12-24 17:55:03.736366001 -0500
+++ fs/ext4/inode.c.new	2009-12-24 18:02:58.556366024 -0500
@@ -1060,6 +1060,10 @@
 	if (mdb_free) {
 		/* Account for allocated meta_blocks */
 		mdb_claim = EXT4_I(inode)->i_allocated_meta_blocks;
+		if (mdb_free < mdb_claim)
+			ext4_msg(inode->i_sb, KERN_ERR, "inode #%lu: "
+				 "mdb_free (%d) < mdb_claim (%d) BUG\n",
+				 inode->i_ino, mdb_free, mdb_claim);
 		BUG_ON(mdb_free < mdb_claim);
 		mdb_free -= mdb_claim;

Then once you get the inode number (suppose it's 12345), please send
the output of the following debugfs commands:

debugfs: stat <12345>
debugfs: ncheck 12345

Thanks!!

					- Ted

  parent reply	other threads:[~2009-12-24 23:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 22:28 2.6.33-rc1: kernel BUG at fs/ext4/inode.c:1063 (sparc) Alexander Beregalov
2009-12-24 22:49 ` Alexander Beregalov
2009-12-25 12:31   ` Dmitry Monakhov
2009-12-25 12:31     ` Dmitry Monakhov
2009-12-25 19:33     ` Alexander Beregalov
2009-12-25 19:33       ` Alexander Beregalov
2009-12-25 23:47       ` Dmitry Monakhov
2009-12-25 23:47         ` Dmitry Monakhov
2009-12-27 20:32         ` Alexander Beregalov
2009-12-27 20:32           ` Alexander Beregalov
2009-12-27 21:38           ` Dmitry Torokhov
2009-12-27 21:38             ` Dmitry Torokhov
2009-12-27 22:52           ` tytso
2009-12-27 23:02             ` Alexander Beregalov
2009-12-27 23:02               ` Alexander Beregalov
2009-12-28  3:51               ` tytso
2009-12-30  5:37                 ` tytso
2009-12-30  5:37                   ` tytso
2009-12-30 13:18                   ` Dmitry Monakhov
2009-12-30 17:45                     ` tytso
2009-12-30 17:48                     ` tytso
2009-12-24 23:05 ` tytso [this message]
2009-12-24 23:15   ` tytso

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=20091224230512.GA32757@thunk.org \
    --to=tytso@mit.edu \
    --cc=a.beregalov@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --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.