Filesystem restored from e2image appears corrupt after replaying journal

Solution Unverified - Updated -

Issue

e2fsck reports serious errors after replaying journal on a e2image:

e2fsck 1.41.14 (22-Dec-2010)
/dev/loop0: recovering journal
e2fsck: Group descriptors look bad... trying backup blocks...
e2fsck: Bad magic number in super-block when using the backup blocks
e2fsck: going back to original superblock
Note: if several inode or block bitmap blocks or part
of the inode table require relocation, you may wish to try
running e2fsck with the '-b 32768' option first.  The problem
may lie only with the primary block group descriptors, and
the backup block group descriptors may be OK.
...

Environment

  • Red Hat Enterprise Linux 5.6
  • Ext3/4 filesystem

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