linux-ext4 - Re: EXT4-fs error (device sdb): ext4_mb_generate_buddy: EXT4-fs: group 1: 912 blocks in bitmap, 898 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] [day] [month] [year] [list]

Message-ID: <20080519082346.GA27661@skywalker>
Date:	Mon, 19 May 2008 13:53:46 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: EXT4-fs error (device sdb): ext4_mb_generate_buddy: EXT4-fs:
	group 1: 912 blocks in bitmap, 898 in gd

Mingming,

On Sun, May 18, 2008 at 02:06:26AM +0530, Aneesh Kumar K.V wrote:
> After almost 15 minutes into the test
> 
> dd if=/dev/zero of=test bs=1M count=51200
> 
> Ext4 file system mounted with -o noextents gives me 
> 
> 
> EXT4-fs error (device sdb): ext4_mb_generate_buddy: EXT4-fs: group 1: 912 blocks in bitmap, 898 in gd
> 
> Call Trace:
> [c0000000e64f6ac0] [c00000000000fbe0] .show_stack+0x70/0x1bc (unreliable)
> [c0000000e64f6b70] [c0000000001a0674] .ext4_error+0x74/0x9c
> [c0000000e64f6c10] [c0000000001ad490] .ext4_mb_init_cache+0x5d0/0x95c
> [c0000000e64f6d80] [c0000000001aeb04] .ext4_mb_load_buddy+0x24c/0x350
> [c0000000e64f6e30] [c0000000001b04d0] .ext4_mb_regular_allocator+0x4fc/0xe08
> [c0000000e64f6f70] [c0000000001b3acc] .ext4_mb_new_blocks+0x158/0x700
> [c0000000e64f7040] [c000000000191f58] .ext4_new_blocks+0xc4/0xf8
> [c0000000e64f7140] [c0000000001963dc] .ext4_get_blocks_handle+0x444/0xb60
> [c0000000e64f7320] [c000000000196c50] .ext4_get_blocks_wrap+0x158/0x1cc
> [c0000000e64f73f0] [c000000000196fd8] .ext4_get_block+0xd0/0x140
> [c0000000e64f74b0] [c000000000112804] .__block_prepare_write+0x1f8/0x4a8
> [c0000000e64f75f0] [c000000000112bc0] .block_write_begin+0xa8/0x13c
> [c0000000e64f76b0] [c000000000198cf0] .ext4_write_begin+0x128/0x240
> [c0000000e64f77b0] [c0000000000a941c] .generic_file_buffered_write+0x154/0x708
> [c0000000e64f78f0] [c0000000000a9d48] .__generic_file_aio_write_nolock+0x378/0x3ec
> [c0000000e64f79f0] [c0000000000a9e3c] .generic_file_aio_write+0x80/0x114
> [c0000000e64f7ab0] [c000000000192d60] .ext4_file_write+0xc8/0x180
> [c0000000e64f7b60] [c0000000000e3a3c] .do_sync_write+0xc4/0x124
> [c0000000e64f7cf0] [c0000000000e4264] .vfs_write+0xd8/0x1bc
> [c0000000e64f7d90] [c0000000000e4be0] .sys_write+0x4c/0x8c
> [c0000000e64f7e30] [c00000000000872c] syscall_exit+0x0/0x40
> 

I guess the below patch needs more testing. Can you make sure it is not
pushed upstream soon.

ext4-use-inode-preallocation-with-noextents.patch

-aneesh
--
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