From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy
Date: Fri, 2 Nov 2012 16:45:07 +0000 (UTC) [thread overview]
Message-ID: <20121102164507.2CC0411FB6C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42723-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42723
--- Comment #13 from Eric Sandeen <sandeen@redhat.com> 2012-11-02 16:45:06 ---
(In reply to comment #12)
> _Fedora-17-x86_6: recovering journal
Hm wonder why the journal was dirty ?
clearing orphaned inodes is fine
> Pass 1: Checking inodes, blocks, and sizes
> Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
> Inode 791 was part of the orphaned inode list. FIXED.
> Inode 1716 was part of the orphaned inode list. FIXED.
> Inode 36947 was part of the orphaned inode list. FIXED.
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Block bitmap differences: +(1262130--1262131) +1313070 -(1685212--1685213)
> Fix<y>? yes
> Free blocks count wrong for group #40 (11881, counted=11880).
> Fix<y>? yes
> Free blocks count wrong (11735574, counted=11735652).
> Fix<y>? yes
Those might have led to the errors you saw, let's see if that clears up the
runtime errors.
-Eric
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-11-02 16:45 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 [this message]
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=20121102164507.2CC0411FB6C@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.