After a crash, fsck on the file system shows "Free blocks count wrong"

Solution Unverified - Updated -

Issue

  • After crash/uncontrolled shutdown, fsck on the file system shows "Free blocks count wrong"
# fsck -nvf /dev/vdb1 
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
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
Block bitmap differences:  +(101725--163839) +164481 +(165888--229375) +(231424--237608)
Fix? no

Free blocks count wrong (2345109, counted=2476898).
Fix? no

Environment

  • Red Hat Enterprise Linux 6
  • FSCK option not enabled in /etc/fstab for the filesystem
  • EXT4 filesystem.
  • WRITE IO occurring on the filesystem at the time of crash

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.