[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120607225446.GK19839@thunk.org>
Date: Thu, 7 Jun 2012 18:54:46 -0400
From: Ted Ts'o <tytso@....edu>
To: Kees Cook <keescook@...omium.org>
Cc: djwong@...ibm.com, Sander Eikelenboom <linux@...elenboom.it>,
Linus Torvalds <torvalds@...ux-foundation.org>,
dm-devel@...hat.com, linux-ext4@...r.kernel.org,
linux-kernel@...r.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
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists