linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy
Date: Thu, 21 Aug 2014 09:21:35 +0000	[thread overview]
Message-ID: <bug-42723-13602-uRdTfwxu55@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-42723-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42723

--- Comment #25 from Zhiyong Wu <zwu.kernel@gmail.com> ---
Hi, Ted

I checked debian 7.5/6 kernel src code, it hasn't merged commit 007649375f6af2
,so this issue whih i met seems to be not caused by this commit.

(In reply to Theodore Tso from comment #23)
> Zhiyong,

The ext4_mb_generate_buddy() error message just means that there
> is an inconsistency between the allocation bitmap and the allocation
> statistics in the block group descriptor.   So people who just google for
> "ext4_mb_generate_buddy" can often find old bugs that had similar symptoms.
> The most recent bugfix in this area was caused by a backport of commit:
> 007649375f6af2 ext4: initialize multi-block allocator before checking block
> descriptors

which caused errors after a replay.  It was reverted in
> mainline commit:

f9ae9cf5d72b39 ext4: revert commit which was causing fs
> corruption after journal replays

You might want to check to see if that
> might be applicable for your kernel.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2014-08-21  9:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 23:10 [Bug 42723] New: EXT4-fs error: ext4_mb_generate_buddy bugzilla-daemon
2012-02-10  1:09 ` [Bug 42723] " bugzilla-daemon
2012-02-20 12:12 ` bugzilla-daemon
2012-04-16  0:21 ` bugzilla-daemon
2012-05-09 18:03 ` bugzilla-daemon
2012-05-14  4:55 ` bugzilla-daemon
2012-10-29 20:25 ` bugzilla-daemon
2012-10-30 20:07 ` bugzilla-daemon
2012-10-30 20:55 ` bugzilla-daemon
2012-10-31  0:53 ` bugzilla-daemon
2012-11-02 15:20 ` bugzilla-daemon
2012-11-02 16:17 ` bugzilla-daemon
2012-11-02 16:43 ` bugzilla-daemon
2012-11-02 16:45 ` bugzilla-daemon
2012-11-02 16:56 ` bugzilla-daemon
2013-03-05  0:18 ` bugzilla-daemon
2013-06-01  9:22 ` bugzilla-daemon
2014-07-05  8:28 ` bugzilla-daemon
2014-07-05  8:41 ` bugzilla-daemon
2014-07-05 13:53 ` bugzilla-daemon
2014-07-06 19:42 ` bugzilla-daemon
2014-08-05  5:06 ` bugzilla-daemon
2014-08-05  9:13 ` bugzilla-daemon
2014-08-05 12:38 ` bugzilla-daemon
2014-08-06  3:45 ` bugzilla-daemon
2014-08-21  9:21 ` bugzilla-daemon [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=bug-42723-13602-uRdTfwxu55@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).