From: Andi Kleen <andi@firstfloor.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Kees Cook <keescook@chromium.org>, "Ted Ts'o" <tytso@mit.edu>,
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: Tue, 05 Jun 2012 16:37:38 -0700 [thread overview]
Message-ID: <m2aa0hjpod.fsf@firstfloor.org> (raw)
In-Reply-To: <1018371644.20120605224154@eikelenboom.it> (Sander Eikelenboom's message of "Tue, 5 Jun 2012 22:41:54 +0200")
Sander Eikelenboom <linux@eikelenboom.it> writes:
>
> Hmm that seems consistent with this report which mentions 3.1.5 as last working kernel:
> http://comments.gmane.org/gmane.comp.file-systems.ext4/30575
>
> So somehow this only effects ext4 on DM (it's THE common factor in all reports) and fsck seems incapable of seeing the error (and thus repair it.)
I have a system that throws this error all the time and it's not using
DM.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-06-05 23:37 UTC|newest]
Thread overview: 17+ 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
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-05 23:37 ` Andi Kleen [this message]
[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=m2aa0hjpod.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=dm-devel@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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