fsck error "programming error? block #????? claimed for no reason in process_bad_block."

Solution Verified - Updated -

Issue

  • During fsck on a corrupted filesystem (possibly cannot be mounted), an error that looks like this is output by fsck, and the filesystem check does not continue/complete:
programming error? block #????? claimed for no reason in process_bad_block.

where "?????" is a block number preceded by the # sign.

Environment

  • Red Hat Enterprise Linux (RHEL) 4,5,6
  • Ext2/3/4 filesystem

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
Close

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