linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	dm-devel@redhat.com, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1904, 32254 clusters in bitmap, 32258 in gd
Date: Mon, 4 Jun 2012 18:26:46 -0400	[thread overview]
Message-ID: <20120604222646.GA6525@thunk.org> (raw)
In-Reply-To: <471046920.20120604234941@eikelenboom.it>

On Mon, Jun 04, 2012 at 11:49:41PM +0200, Sander Eikelenboom wrote:
> Hello Ted,
> 
> I have enabled some debug options, this is from around when the error occurs (kernel: [  950.610126] EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1699, 32254 clusters in bitmap, 32258 in gd)

This error is usually caused by a filesystem corruption; specifically,
either a corrupted block allocation bitmap or a corrupted block group
descriptor.  This error means that number of bits set in the block
allocation bitmap (32254) doesn't match the number that is reflected
in the summary block group descriptor statistics (32258).

I should probably change this error message so it's clearer what this
means to civilians.

If you run e2fsck on the file system, it will fix the file system
corruption.  If you can reliably reproduce the problem after e2fsck is
run, that would be useful to know.

Regards,

						- Ted

  reply	other threads:[~2012-06-04 22:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 21:49 EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1904, 32254 clusters in bitmap, 32258 in gd Sander Eikelenboom
2012-06-04 22:26 ` Ted Ts'o [this message]
2012-06-05  0:03 ` Kees Cook
2012-06-05 20:41   ` Sander Eikelenboom
2012-06-05 21:08     ` Ted Ts'o
2012-06-05 21:35       ` Sander Eikelenboom
2012-06-06  7:01       ` Sander Eikelenboom
2012-06-06 14:32         ` Kees Cook
2012-06-06 14:40           ` Sander Eikelenboom
2012-06-07  4:27             ` Ted Ts'o
2012-06-07 22:27               ` [dm-devel] " djwong
2012-06-07 22:40                 ` Kees Cook
2012-06-07 22:54                   ` Ted Ts'o
2012-06-07 23:38                     ` Kees Cook
2012-06-08  4:43                       ` Andreas Dilger
2012-06-05 23:37     ` Andi Kleen
     [not found] <17610219749.20120604192048@eikelenboom.it>
2012-06-04 23:04 ` Ted Ts'o
2012-06-05  6:56   ` Sander Eikelenboom

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=20120604222646.GA6525@thunk.org \
    --to=tytso@mit.edu \
    --cc=dm-devel@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).