From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy
Date: Mon, 20 Feb 2012 12:12:23 GMT [thread overview]
Message-ID: <201202201212.q1KCCNfx010492@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42723-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42723
Pekka Pietikäinen <pp@ee.oulu.fi> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pp@ee.oulu.fi
--- Comment #2 from Pekka Pietikäinen <pp@ee.oulu.fi> 2012-02-20 12:12:22 ---
I've potentially seen this with 3.2.1/3.2.5 (Fedora 16)
messages-20120219:Feb 16 18:11:40 laptop kernel: [688848.718886] EXT4-fs error
(device dm-1): mb_free_blocks:1348: group 28, block 924740:freeing already
freed block (bit 7236)
messages-20120219:Feb 16 18:11:40 laptop kernel: [688848.718890] EXT4-fs error
(device dm-1): mb_free_blocks:1348: group 28, block 924741:freeing already
freed block (bit 7237)
...
messages:Feb 19 04:46:02 laptop kernel: [106683.790999] EXT4-fs error (device
dm-1): ext4_mb_generate_buddy:739: group 311, 15861 clusters in bitmap, 9309 in
gd
messages:Feb 19 04:46:02 laptop kernel: [106683.874849] EXT4-fs error (device
dm-1): ext4_mb_generate_buddy:739: group 321, 30343 clusters in bitmap, 30295
in gd
but... the laptop in question is a quite dodgy hardware-wise (wiggle the case a
bit and the Thinklight blinks etc.). Typical light laptop use with root/home on
LVM the way Fedora puts them by default.
So far it's getting ext4 errors every few days, reboot & fsck and it's fine for
a while, running 3.2.6 now.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-20 12:12 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 [this message]
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
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=201202201212.q1KCCNfx010492@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).