I've got a 2TiB Ext3-FS on a SAN via Qlogic cards.  Upon mounting, the kernel spewed out the following:

EXT3-fs error (device lvm(58,0)): ext3_check_descriptors: \
Inode bitmap for group 0 not in group (block 178114594)!
EXT3-fs: group descriptors corrupted !
EXT3-fs: Magic mismatch, very weird !

It's currently fscking, and I've gone through thousands of errors similar to the following:

Inode 131881105 is in use, but has dtime set.  Fix<y>? yes
Inode 131881106 was part of the orphaned inode list.  FIXED.
Inode 131881107 was part of the orphaned inode list.  FIXED.
Inode 131881109 was part of the orphaned inode list.  FIXED.
Deleted inode 131881110 has zero dtime.  Fix<y>? yes
Inode 131881111 is in use, but has dtime set.  Fix<y>? yes
Inode 131881111 has imagic flag set.  Clear<y>? yes
Inode 131881112 is in use, but has dtime set.  Fix<y>? yes
Inode 131881113 was part of the orphaned inode list.  FIXED.
Inode 131881114 was part of the orphaned inode list.  FIXED.
Inode 131881115 was part of the orphaned inode list.  FIXED.
Inode 131881116 was part of the orphaned inode list.  FIXED.
Deleted inode 131881117 has zero dtime.  Fix<y>? yes
Inode 131881118 is in use, but has dtime set.  Fix<y>? yes
Inode 131881118 has imagic flag set.  Clear<y>? yes
Inode 131881119 is in use, but has dtime set.  Fix<y>? yes
Inode 131881120 was part of the orphaned inode list.  FIXED.
Inode 131881091, i_blocks is 66, should be 0.  Fix<y>? yes
Inode 131881098, i_blocks is 66, should be 0.  Fix<y>? yes
Inode 131881105, i_blocks is 66, should be 0.  Fix<y>? yes
Inode 131881112 has compression flag set on filesystem without compression support. \
Clear<y>? yes
Inode 131881112, i_blocks is 13, should be 0.  Fix<y>? yes
Inode 131881119 has compression flag set on filesystem without compression support. \
Clear<y>? yes
Inode 131881119, i_blocks is 15, should be 0.  Fix<y>? yes
Inode 131881115 has compression flag set on filesystem without compression support. \
Clear<y>? yes
Inode 131881115 has INDEX_FL flag set but is not a directory.
Clear HTree index<y>? yes
/dev/vg/lv: |==========================                      / 53.9%

Think it'll make it?  Only time (and lots of it) will tell, but I'm thinking no.

New comments are currently disabled for this entry.