All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Frank Mayhar <fmayhar@google.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	Curt Wohlgemuth <curtw@google.com>, mrubin <mrubin@google.com>
Subject: Re: ext4_mb_generate_buddy and double-free errors
Date: Thu, 12 Mar 2009 22:25:10 -0500	[thread overview]
Message-ID: <49B9D216.8040401@redhat.com> (raw)
In-Reply-To: <1236914533.731.15.camel@bobble.smo.corp.google.com>

Frank Mayhar wrote:
> On Thu, 2009-03-12 at 21:03 -0500, Eric Sandeen wrote:
>> Frank Mayhar wrote:
>>> We're seeing errors like:
>>>   EXT4-fs error (device sda3): ext4_mb_generate_buddy: EXT4-fs: group 3049: 21020 blocks in bitmap, 21529 in gd
>>>
>>> Usually after this the system is cleaned and in the process we see many
>>> "mb_free_blocks: double-free of inode x's block y(bit z in group d)".
>>> (In fact, we see exactly as many of these as the difference between the
>>> group and computed count of free blocks.)
>>>
>>> It looks like the bitmap itself is getting messed up somehow, at least
>>> enough to make the free count disagree with the map itself.  Has anyone
>>> else seen something like this?  Any pointers as to where to look for
>>> potential culprits?
>> Which kernel, for starters?
> 
> It's our development kernel, 2.6.26 plus as many of the ext4/jbd2
> patches as we can comfortably pull in.

which makes it a little tough; can you test on upstream too to see if it
persists?

At this point you are becoming your own distribution (but I suppose you
are used to that) ;)

-Eric

  reply	other threads:[~2009-03-13  3:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13  0:29 ext4_mb_generate_buddy and double-free errors Frank Mayhar
2009-03-13  2:03 ` Eric Sandeen
2009-03-13  3:22   ` Frank Mayhar
2009-03-13  3:25     ` Eric Sandeen [this message]
2009-03-13  3:32       ` Curt Wohlgemuth

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=49B9D216.8040401@redhat.com \
    --to=sandeen@redhat.com \
    --cc=curtw@google.com \
    --cc=fmayhar@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mrubin@google.com \
    /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.