From: tytso@mit.edu
To: Alexander Beregalov <a.beregalov@gmail.com>,
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:15:11 -0500 [thread overview]
Message-ID: <20091224231511.GB32757@thunk.org> (raw)
In-Reply-To: <20091224230512.GA32757@thunk.org>
On Thu, Dec 24, 2009 at 06:05:12PM -0500, tytso@MIT.EDU wrote:
> 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:
Here's a revised version of the patch which should avoid the BUG_ON,
which should make it be less annoying. We should really figure out
what's going on and fix it, though. It may be fixed by the recently
pushed quota race fixes, or at least there's a good chace that it's
related to a ext4 quota-releated WARN_ON that people have been
complaining about.
- Ted
--- /tmp/inode.c 2009-12-24 17:55:03.736366001 -0500
+++ /tmp/inode.c.new 2009-12-24 18:13:07.716366002 -0500
@@ -1060,8 +1060,14 @@
if (mdb_free) {
/* Account for allocated meta_blocks */
mdb_claim = EXT4_I(inode)->i_allocated_meta_blocks;
- BUG_ON(mdb_free < mdb_claim);
- mdb_free -= mdb_claim;
+ 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);
+ WARN_ON(1);
+ mdb_free = 0;
+ } else
+ mdb_free -= mdb_claim;
/* update fs dirty blocks counter */
percpu_counter_sub(&sbi->s_dirtyblocks_counter, mdb_free);
prev parent reply other threads:[~2009-12-24 23:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 22:28 Alexander Beregalov
2009-12-24 22:49 ` Alexander Beregalov
2009-12-25 12:31 ` Dmitry Monakhov
2009-12-25 19:33 ` Alexander Beregalov
2009-12-25 23:47 ` Dmitry Monakhov
2009-12-27 20:32 ` Alexander Beregalov
2009-12-27 21:38 ` Dmitry Torokhov
2009-12-27 22:52 ` tytso
2009-12-27 23:02 ` Alexander Beregalov
2009-12-28 3:51 ` 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
2009-12-24 23:15 ` tytso [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=20091224231511.GB32757@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®