* Ext3 error with Megaraid on x86_64 with 8GB RAM
@ 2005-11-02 13:20 bloch
2005-11-02 13:45 ` bloch
0 siblings, 1 reply; 3+ messages in thread
From: bloch @ 2005-11-02 13:20 UTC (permalink / raw)
To: linux-kernel
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.
I'd appreciate any suggestions on tracking down this problem.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Ext3 error with Megaraid on x86_64 with 8GB RAM
2005-11-02 13:20 Ext3 error with Megaraid on x86_64 with 8GB RAM bloch
@ 2005-11-02 13:45 ` bloch
2005-11-02 18:03 ` Evgeny Rodichev
0 siblings, 1 reply; 3+ messages in thread
From: bloch @ 2005-11-02 13:45 UTC (permalink / raw)
To: linux-kernel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Ext3 error with Megaraid on x86_64 with 8GB RAM
2005-11-02 13:45 ` bloch
@ 2005-11-02 18:03 ` Evgeny Rodichev
0 siblings, 0 replies; 3+ messages in thread
From: Evgeny Rodichev @ 2005-11-02 18:03 UTC (permalink / raw)
To: bloch; +Cc: linux-kernel
On Wed, 2 Nov 2005, bloch@verdurin.com wrote:
> 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.
The problem looks very similar to my problem with Opteron and 8G RAM.
Please send the output from lspci -v and dmesg
_________________________________________________________________________
Evgeny Rodichev Sternberg Astronomical Institute
email: er@sai.msu.su Moscow State University
Phone: 007 (095) 939 2383
Fax: 007 (095) 932 8841 http://www.sai.msu.su/~er
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-11-02 18:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-11-02 13:20 Ext3 error with Megaraid on x86_64 with 8GB RAM bloch
2005-11-02 13:45 ` bloch
2005-11-02 18:03 ` Evgeny Rodichev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®