[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

EXT3-fs: invalid journal inode.



Hi Everyone,

I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with:

mount: wrong fs type, bad option, bad superblock on /dev/sdb,
       missing codepage or other error

dmesg reports:
EXT3-fs: invalid journal inode.

I tried to run e2fsck and it failed (The output can be seen below).

If anyone has any suggestions on how I can restore the filesystem I would greatly appreciate the help.

Thanks in advance,
Sabin




*** BEGIN e2fsck output *****

root 0[sabin]# e2fsck -b 32768 /dev/sdb
e2fsck 1.38 (30-Jun-2005)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock doesn't have has_journal flag, but has ext3 journal inode.
Clear<y>? yes

/dev/sdb was not cleanly unmounted, check forced.
e2fsck: Illegal doubly indirect block found while reading bad blocks inode
This doesn't bode well, but we'll try to go on...
Pass 1: Checking inodes, blocks, and sizes
Bad block inode has illegal block(s).  Clear<y>? yes

Illegal block #9 (2933653514) in bad block inode.  CLEARED.
Group 32's block bitmap (1048576) is bad.  Relocate<y>? yes

Block 8 in the primary group descriptors is on the bad block list

If the block is really bad, the filesystem can not be fixed.
You can remove this block from the bad block list and hope
that the block is really OK.  But there are no guarantees.

Clear<y>? yes

Bad block inode has an indirect block (1048577) that conflicts with
filesystem metadata.  CLEARED.
Bad block inode has an indirect block (1048576) that conflicts with
filesystem metadata.  CLEARED.

The bad block inode has probably been corrupted.  You probably
should stop now and run e2fsck -c to scan for bad blocks
in the filesystem.
Continue<y>? no

e2fsck: aborted
root 0[sabin]# e2fsck -c  /dev/sdb
e2fsck 1.38 (30-Jun-2005)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Superblock doesn't have has_journal flag, but has ext3 journal inode.
Clear<y>? yes

Inode count in superblock is 151584768, should be 152633344.
Fix<y>? yes

ext2fs_block_iterate: Ext2 file too big while sanity checking the bad blocks inode



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]