From: Ted Ts'o <tytso@mit.edu>
To: Kees Cook <keescook@chromium.org>
Cc: djwong@us.ibm.com, Sander Eikelenboom <linux@eikelenboom.it>,
Linus Torvalds <torvalds@linux-foundation.org>,
dm-devel@redhat.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1904, 32254 clusters in bitmap, 32258 in gd
Date: Thu, 7 Jun 2012 18:54:46 -0400 [thread overview]
Message-ID: <20120607225446.GK19839@thunk.org> (raw)
In-Reply-To: <CAGXu5jKmBkfvuSR7q47-Ac57dVZynz_JkYXiA_-aXaGQiR_C4g@mail.gmail.com>
On Thu, Jun 07, 2012 at 03:40:40PM -0700, Kees Cook wrote:
>
> FWIW, I was building the filesystem that triggered this as ext4:
>
> mkfs.ext4 -T default -m 0 -O ^huge_file,^flex_bg -E
> discard,lazy_itable_init /dev/mapper/...
Ouy of curiosity, was there a reason you chose those particular file
system parameters? It's a surprising set, because if you're starting
with a fresh file system, enabling flex_bg produces a more optimal
file system layout.
The reason why I wrote the commit description way I did was because it
seemed to be the most likely way that someone would trip across this
bug. We didn't notice this for as long as we did since most of the
users of ext4 (especially those who use community distributions) have
been using freshly mkfs'ed ext4 file systems.
- Ted
next prev parent reply other threads:[~2012-06-07 22:54 UTC|newest]
Thread overview: 16+ 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 [this message]
2012-06-07 23:38 ` Kees Cook
2012-06-08 4:43 ` Andreas Dilger
2012-06-05 23:37 ` Andi Kleen
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=20120607225446.GK19839@thunk.org \
--to=tytso@mit.edu \
--cc=djwong@us.ibm.com \
--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 \
/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).