From: Dave Chinner <david@fromorbit.com>
To: linux-ext4@vger.kernel.org
Subject: [4.7-rc6 ext3 corruption] ext4_mb_generate_buddy:758: group 27, block bitmap and bg descriptor inconsistent:
Date: Tue, 12 Jul 2016 15:41:37 +1000 [thread overview]
Message-ID: <20160712054137.GI1922@dastard> (raw)
Hi Folks,
Just rebooted a 4.7-rc6 test VM, and the root filesystem had the
journal abort a couple of seconds after mount while the system was
still booting:
[ 3.043543] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 3.045027] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 3.046008] EXT4-fs (sda1): write access will be enabled during recovery
[ 3.120052] EXT4-fs (sda1): recovery complete
[ 3.121746] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 3.122778] VFS: Mounted root (ext3 filesystem) readonly on device 8:1.
.....
[ 5.263329] EXT4-fs error (device sda1): ext4_mb_generate_buddy:758: group 27, block bitmap and bg descriptor inconsistent: 4197 vs 4196 free clusters
[ 5.266343] Aborting journal on device sda1-8.
[ 5.267939] EXT4-fs (sda1): Remounting filesystem read-only
[ 5.269129] EXT4-fs error (device sda1) in ext4_free_blocks:4904: Journal has aborted
[ 5.271431] EXT4-fs error (device sda1) in ext4_do_update_inode:4891: Journal has aborted
[ 5.273720] EXT4-fs error (device sda1) in ext4_truncate:4150: IO failure
[ 5.275917] EXT4-fs error (device sda1) in ext4_orphan_del:2923: Journal has aborted
[ 5.278325] EXT4-fs error (device sda1) in ext4_do_update_inode:4891: Journal has aborted
The root filesystem checked clean three reboots before this
occurred. e2fsck output on ro mounted fs:
# e2fsck /dev/sda1
e2fsck 1.43-WIP (18-May-2015)
/dev/sda1: recovering journal
Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set)
/dev/sda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (542319, counted=546517).
Fix<y>? yes
Inode bitmap differences: -219131
Fix<y>? yes
Free inodes count wrong for group #27 (6720, counted=6721).
Fix<y>? yes
Directories count wrong for group #27 (9, counted=8).
Fix<y>? yes
Free inodes count wrong (341015, counted=341018).
Fix<y>? yes
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: ***** REBOOT LINUX *****
/dev/sda1: 283606/624624 files (3.1% non-contiguous), 1949574/2496091 blocks
#
--
Dave Chinner
david@fromorbit.com
next reply other threads:[~2016-07-12 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 5:41 Dave Chinner [this message]
2016-07-27 15:48 ` [4.7-rc6 ext3 corruption] ext4_mb_generate_buddy:758: group 27, block bitmap and bg descriptor inconsistent: Jan Kara
2016-07-27 23:57 ` Dave Chinner
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=20160712054137.GI1922@dastard \
--to=david@fromorbit.com \
--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