From: Ted Ts'o <tytso@mit.edu>
To: Robin Dong <hao.bigrat@gmail.com>
Cc: linux-ext4@vger.kernel.org, Robin Dong <sanbai@taobao.com>,
Tao Ma <boyu.mt@taobao.com>
Subject: Re: [PATCH] ext4: critical info format fix in __ext4_grp_locked_error
Date: Mon, 21 Mar 2011 20:47:39 -0400 [thread overview]
Message-ID: <20110322004739.GJ4135@thunk.org> (raw)
In-Reply-To: <1300442283-31421-1-git-send-email-hao.bigrat@gmail.com>
Applied to the ext4 patch queue.
On Fri, Mar 18, 2011 at 05:58:03PM +0800, Robin Dong wrote:
> From: Robin Dong <sanbai@taobao.com>
>
> When we do performence-testing on ext4 filesystem, we observe a warning like this:
>
> "[ 1684.113205] EXT4-fs error (device sda7): ext4_mb_generate_buddy:718: group 259825901 blocks in bitmap, 26057 in gd"
>
> indeed, it should be
>
> "group 2598, 25901 blocks in bitmap, 26057 in gd"
Note that the next two paragraphs don't really belong in a commit
description. It's best if you put this kind of stuff after the
signed-off-by lines, with a "---" separating the commit description, like this:
Signed off by: Ty Coon <tycoon@gmail.com>
---
Stuff that explains the context of the patch
diff --git ....
> This bug is found on upstream 2.6.36 kernel. We ran a 2.6.36 kernel
> on the online system with 8 Ext4 file systems. 2 of them are mounted
> with delayed allocation feature. This warning is only observed on
> delayed allocation enabled Ext4 file systems.
>
> This issue is not easy to reproduce, on two servers with 2.6.36
> kenrel + ext4, after running 110+ days, the error starts to appear
> on kernel log. When check the error log, we found the info format
> should be fixed, that's how this patch comes.
Can you send more information about what sort of workloads your
servers are under, and any other information about how to reproduce
it?
- Ted
next prev parent reply other threads:[~2011-03-22 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 9:58 [PATCH] ext4: critical info format fix in __ext4_grp_locked_error Robin Dong
2011-03-22 0:47 ` Ted Ts'o [this message]
2011-03-22 2:30 ` Tao Ma
2011-03-22 5:35 ` Coly Li
-- strict thread matches above, loose matches on Subject: below --
2011-03-17 1:56 Robin Dong
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=20110322004739.GJ4135@thunk.org \
--to=tytso@mit.edu \
--cc=boyu.mt@taobao.com \
--cc=hao.bigrat@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sanbai@taobao.com \
/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).