I'm looking for some recommendations on where to go with a problem i'm running across. A filesystem under load put itself in readonly mode and the following can be found under dmesg.. any suggestions on root cause? hardware wise it's got a pair of PATA drives connected to a 3ware card in RAID10 configuration. EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory #14370410: rec_len % 4 != 0 - offset=0, inode=1309281588, rec_len=16761, name_len=78 Aborting journal on device dm-4. ext3_abort called. EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-4) in start_transaction: Journal has aborted EXT3-fs error (device dm-4) in ext3_create: IO failure __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data
Gerald wrote:> I'm looking for some recommendations on where to go with a problem i'm > running across. A filesystem under load put itself in readonly mode > and the following can be found under dmesg.. any suggestions on root > cause? hardware wise it's got a pair of PATA drives connected to a > 3ware card in RAID10 configuration.a pair? or two pairs?> > EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory > #14370410: rec_len % 4 != 0 - offset=0, inode=1309281588, > rec_len=16761, name_len=78 > Aborting journal on device dm-4. > ext3_abort called. > EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > EXT3-fs error (device dm-4) in start_transaction: Journal has aborted > EXT3-fs error (device dm-4) in ext3_create: IO failure > __journal_remove_journal_head: freeing b_committed_data > __journal_remove_journal_head: freeing b_committed_datadata=journal?