From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy
Date: Tue, 05 Aug 2014 09:13:16 +0000 [thread overview]
Message-ID: <bug-42723-13602-BPA44HQ90h@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 #22 from Zhiyong Wu <zwu.kernel@gmail.com> ---
When trying to run fsck, i got the similar info:
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
/dev/xvda1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 265617 has zero dtime. Fix<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
Inode 917518 was part of the orphaned inode list. FIXED.
Inode 917533 was part of the orphaned inode list. FIXED.
Inode 917537 was part of the orphaned inode list. FIXED.
Inode 917539 was part of the orphaned inode list. FIXED.
Inode 917541 was part of the orphaned inode list. FIXED.
Deleted inode 917545 has zero dtime. Fix<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(41472--41862) -(41920--41952) -(42464--42485)
-(53184--53217) -(1092376--1092379) -(1092388--
1092399)
Fix<y>? yes
Inode bitmap differences: -265617 -917518 -917533 -917537 -917539 -917541
-917545
Fix<y>? yes
Free inodes count wrong for group #32 (1429, counted=1430).
Fix<y>? yes
Free inodes count wrong (1273982, counted=1273983).
Fix<y>? yes
/dev/xvda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/xvda1: ***** REBOOT LINUX *****
/dev/xvda1: 36737/1310720 files (0.2% non-contiguous), 359493/5242368 blocks
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-08-05 9:13 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 [this message]
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=bug-42723-13602-BPA44HQ90h@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).