On Tue, 01 Nov 2005, bloch@xxxxxxxxxxxx wrote: > > As an update to this, the problem seems to have re-occurred. Here are > the relevant error messages: > > EXT3-fs error (device sdb1): ext3_new_block: Allocating block in system > zone - block = 41484288 > Aborting journal on device sdb1. > EXT3-fs error (device sdb1) in ext3_new_block: Journal has aborted > ext3_abort called. > EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > EXT3-fs error (device sdb1) in ext3_reserve_inode_write: Journal has > aborted > __journal_remove_journal_head: freeing b_committed_data > Another update - exactly the same problem has occurred on an identical machine. The disks are on a Megaraid RAID1 array. Two other machines which only differ from the problem ones in that they have 4G RAM instead of 8G have not shown any such symptoms. Adam _______________________________________________ Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
