Ext3 error on RedHat 4.0 AS

[Cliff Lim Kok Hwee]

Hi Forum,

I recently untar 1 filesystem from 1 server into another server running RedHat 4.0 AS. This houses Oracle Application.

Recently, was encountered the following errors:

- EXT3-fs error (device md5): ext3_free_blocks_sb: bit already cleared for block 1303980 Aborting journal on device md5. ext3_abort called. EXT3-fs error (device md5): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only

Only way was reboot the server and then it become ok. On my scenerio, the filesystem screw up upon a reboot and WE GOT NO BACKUP :)

Need any advise.
Cliff

[Ivan Ferreira]

Your md device is IDE or SCSI? A reboot may clean the filesystem if a fsck was runned. You should force a fsck to check for file system inconsistences.

[Cliff Lim Kok Hwee]

Hi Dudes, I see alot of reports on ext3 - mounting read-only on the net. But wondering n need to know wht is actually causing it. That worry me alot man. Solution of fsck is fine. But is the sudden readonly that is not HEALTHY and RISKY. Data will just be GONE if fsck fails. Any pre-emptive measures? Was thinking of logging redhat a call. Cliff

[Vitaly Karasik_1]

- do you see something interesting in "dmesg" output and/or into /var/log/messages?
- what do you see under /proc/mdstat?

[dirk dierickx]

log a call with RH. if you paid for their support, you can't get any better then that.

[Alan_152]

get a copy of ubuntu or knoppix Live CD and dd your current drives to new media... don't do anything else until you get a backup...