Re: Linux filesystem turns read-only when creating tablespaces (Oracle 10g) ?

hipo wrote:
> Hi Laurenz,
>
> Thank you for your answer.
>
> Here's the messages file regarding to the error:
>
> Oct 18 15:37:03 ttoracle kernel: journal_bmap: journal block not found
> at offset 1036 on hdb1
> Oct 18 15:37:03 ttoracle kernel: Aborting journal on device hdb1.
> Oct 18 15:37:03 ttoracle kernel: ext3_abort called.
> Oct 18 15:37:03 ttoracle kernel: EXT3-fs error (device hdb1):
> ext3_journal_start_sb: Detected aborted journal
> Oct 18 15:37:03 ttoracle kernel: Remounting filesystem read-only
> Oct 18 15:37:12 ttoracle kernel: __journal_remove_journal_head:
> freeing b_committed_data
> Oct 18 15:37:12 ttoracle kernel: __journal_remove_journal_head:
> freeing b_frozen_data
> Oct 18 15:37:12 ttoracle kernel: __journal_remove_journal_head:
> freeing b_committed_data
> Oct 18 15:37:12 ttoracle kernel: __journal_remove_journal_head:
> freeing b_frozen_data
>
>
> And, yes, I can write a file after restarting the system, and the disk
> seems to be ok again.... but I can't still create the more than 2
> Gbytes tablespace.

One remark: it seems you use a journaling file system on that disk. IMHO this is superfluous if you want to use it for DB only as this duplicates the journaling (the DB does ensure integrity of data itself). This is likely to make things slower. If possible you might want to use that disk as raw device.

Kind regards

    robert Received on Wed Oct 19 2005 - 03:16:49 CDT