EXT3-fs unexpected failure msg ?

Sev Binello sev at bnl.gov
Mon Apr 17 19:22:25 UTC 2006



Hi -

   We have had a raid failure, we have some what recovered
   but we continue to see the following ext3 message...

Apr 17 14:59:14 acnlin84 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << 
BH_Uptodate)) != 0);
Apr 17 14:59:14 acnlin84 kernel: Possible IO failure.


   Since we have experienced several instances of ext3 file system corruption
   when we lose total communication with our raid,
   we were wondering if there was any concrete advice out there
   on what to do in this situation.

Other messages we got before the ones above...
Apr 17 13:40:42 acnlin84 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: bit already 
cleared for block 14943160
Apr 17 13:40:42 acnlin84 kernel: EXT3-fs error (device sd(8,33)): ext3_free_blocks: bit already 
cleared for block 3703794

Apr 17 13:40:43 acnlin84 kernel: EXT3-fs error (device sd(8,65)): ext3_get_inode_loc: unable to read 
inode block - inode=50931914, block=101843272
-- 

Sev Binello
Brookhaven National Laboratory
Upton, New York
631-344-5647
sev at bnl.gov




More information about the Ext3-users mailing list