Red Hat Bugzilla – Bug 170107
Kernel: journal_bmap_Rsmp_579e6c39: journal block not found at offset 1036 on sd(8,33)
Last modified: 2007-11-30 17:07:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; (R1 1.3); .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Description of problem:
After first installation of RH 3.2 on DELL PE2800 with dual Xeon64-Bit, Perc4, two RAID0 and one RAID5 Diskgroups i installed Oracle10g. When setup is completed the Database has to be created. During this, the RAID5 Diskgroup brings the errormessages:
Kernel: journal_bmap_Rsmp_579e6c39: journal block not found at offset 1036 on sd(8,33).
Kernel: Aborting journal on device sd(8,33).
Kernel: Error(-5) on journal on device 08:21.
Kernel: journal commit I/O error
Kernel: ext3_abort called.
Kernel: EXT3-fs abort(device sd(8,33)): ext3_journal_start: Detected aborted journal
Kernel: Remounting filesystem read-only
After this Oracle crashes. I can start Oracle only after a reboot.
The megaraid2 driver and firmware are on aktual state.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
3.start several oracle-scripte. It's not important which scripts. The error occurs after a while whatever i do.
Actual Results: RAID5 - Filesystem switches to read-only. Oracle crashes
For faster service, please file this with Customer Support. They might
be able to detect some sort of problem with your RAID configuration. Let
them know this BZ id so they can link it properly to the Issue Tracker ticket.
In the meantime, I'll assign this to our ext3 maintainer in case he's aware
of some outstanding problem with journal_bmap().