Hi All!

I'm working on SLES9 SP3 (IBM x365), Oracle 10.1.0.4.0. Today my Oracle
crash down because of the one file system (were oracle datafiles are
located) was mounted as ro (read only). In /var/log/warn i saw:

Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240000
Jan 30 01:59:32 sunset kernel: Aborting journal on device dm-1.
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240001
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240002
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240003
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240004
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240005
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240006
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240007
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240008
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240009
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240010
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1):
ext3_free_blocks: bit already cleared for block 10240011
Jan 30 01:59:32 sunset kernel: ext3_reserve_inode_write: aborting
transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device
dm-1) in ext3_reserve_inode_write: Journal has aborted
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1) in
ext3_truncate: Journal has aborted
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1) in
ext3_orphan_del: Journal has aborted
Jan 30 01:59:32 sunset kernel: EXT3-fs error (device dm-1) in
ext3_delete_inode: Journal has aborted
Jan 30 01:59:32 sunset last message repeated 2 times
Jan 30 01:59:32 sunset kernel: __journal_remove_journal_head: freeing
b_committed_data
Jan 30 01:59:32 sunset kernel: ext3_abort called.
Jan 30 01:59:33 sunset kernel: EXT3-fs abort (device dm-1):
ext3_journal_start: Detected aborted journal
Jan 30 01:59:33 sunset kernel: Remounting filesystem read-only
Jan 30 02:02:27 sunset kernel: ext3_abort called.
Jan 30 02:02:27 sunset kernel: EXT3-fs abort (device dm-1):
ext3_remount: Abort forced by user
Jan 30 02:02:27 sunset kernel: ext3_abort called.
Jan 30 02:02:27 sunset kernel: EXT3-fs abort (device dm-1):
ext3_remount: Abort forced by user
Jan 30 03:17:08 sunset kernel: __journal_remove_journal_head: freeing
b_committed_data

After that I check this fs with fsck and mount. Now all works fine, but
i worry about my db.

Any suggestion?

--
Andrew Edunov



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting