From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: EXT4-fs error (device sdb): ext4_mb_generate_buddy: EXT4-fs: group 1: 912 blocks in bitmap, 898 in gd
Date: Mon, 19 May 2008 13:53:46 +0530 [thread overview]
Message-ID: <20080519082346.GA27661@skywalker> (raw)
In-Reply-To: <20080517203625.GA18235@skywalker>
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
prev parent reply other threads:[~2008-05-19 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 20:36 EXT4-fs error (device sdb): ext4_mb_generate_buddy: EXT4-fs: group 1: 912 blocks in bitmap, 898 in gd Aneesh Kumar K.V
2008-05-19 8:23 ` Aneesh Kumar K.V [this message]
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=20080519082346.GA27661@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.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).