linux-ext4 - Re: [dm-devel] EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1904, 32254 clusters in bitmap, 32258 in gd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGXu5jKmBkfvuSR7q47-Ac57dVZynz_JkYXiA_-aXaGQiR_C4g@mail.gmail.com>
Date:	Thu, 7 Jun 2012 15:40:40 -0700
From:	Kees Cook <keescook@...omium.org>
To:	djwong@...ibm.com
Cc:	"Ted Ts'o" <tytso@....edu>,
	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 7, 2012 at 3:27 PM, djwong <djwong@...ibm.com> wrote:
> On Thu, Jun 07, 2012 at 12:27:56AM -0400, Ted Ts'o wrote:
>> I think this patch should fix things.  Could you give it a try (after
>> re-enabling uninit_bg and then running e2fsck on the file systems)?
>>
>> Many thanks,
>>
>>                                               - Ted
>>
>> commit b6b218940d47f20fc14e4d203930c575be0c65bf
>> Author: Theodore Ts'o <tytso@....edu>
>> Date:   Thu Jun 7 00:26:56 2012 -0400
>>
>>     ext4: fix the free blocks calculation for ext3 file systems w/ uninit_bg
>>
>>     Ext3 filesystems that are converted to use as many ext4 file systems
>>     as possible
>
> Just to clarify the description a bit:
>
> Did you mean "..as many ext4 filesystem _features_ as possible" ?
>
>> will enable uninit_bg to speed up e2fsck times.  File
>>     systems with an native ext3 layout of inode tables and block
>
> Perhaps "On file systems with a native ext3 layout..." ?

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/...

-Kees

-- 
Kees Cook
Chrome OS Security
--
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