Messages in this thread | | | Date | Wed, 2 Nov 2005 13:45:01 +0000 | From | bloch@verdurin ... | Subject | Re: Ext3 error with Megaraid on x86_64 with 8GB RAM |
| |
On Wed, 02 Nov 2005, bloch@verdurin.com wrote:
> Three times now I've seen severe ext3 problems on two different Opteron > machines with 8G RAM. Two other machines with 4G are otherwise > identical but haven't exhibited the same filesystem problems. > > The corruption occurs on a Megaraid RAID 1 array. > > Here's the error message: > > EXT3-fs error (device sdb2): ext3_new_block: Allocating block in system > zone - block = 55593720 > Aborting journal on device sdb2. > EXT3-fs error (device sdb2) in ext3_prepare_write: Journal has aborted > ext3_abort called. > EXT3-fs error (device sdb2): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > __journal_remove_journal_head: freeing b_committed_data > > The motherboard is a Tyan Thunder K8W. > > The first time this happened fsck could not fix the errors and I had to > wipe the partition. >
This is with a Fedora 4 kernel 2.6.13-1.1532_FC4smp - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |