Why does fsck keeps looping on ext3 filesystem with an error 'Illegal block #68622 (3042216764) in inode 7. CLEARED?' in Red Hat Enterprise Linux 4

Solution Verified - Updated -

Issue

  • fsck keeps looping on ext3 filesystem. The following are the log messages.

    Illegal block #68942 (1250271298) in inode 7.  CLEARED. 
Illegal block #68943 (1250262350) in inode 7.  CLEARED. 
Illegal block #68944 (1250262350) in inode 7.  CLEARED. 
Illegal block #68974 (1250269601) in inode 7.  CLEARED. 
Too many illegal blocks in inode 7. 
Clear inode? yes

Environment

  • Red Hat Enterprise Linux 4 update 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content