Re: Raw device again

Seems to me your problems are elsewhere. I run a mix of db's, some on raw, some on filesystem, all without the problems you list.

You can go 'partial' or 'all' raw, decision is yours. Redo and anything heavily, sequentially written would be first candidates for raw. Put Archive Log on filesystem, even when you put the rest of the db on raw.

MotoX.

S S Wan wrote in message <6ns8av$dal$1_at_tst.hk.super.net>...
>I recently have a 10 GB database destroyed by
>a filesystem crash. I begin to doubt whether it
>is the choice of filesystem instead of raw device
>that caused prolonged downtime for restore.
>
>I am placing all datafiles, redo log files, archived log
>files in different RAID-5/mirrored filesystems for
>performance purpose. It seems unavoidable
>that a filesystem corruption (even cannot be fsck'ed)
>will destory all files inside. So......if I use raw device,
>will it be better? Since a write to log is always sync'ed,
>the database should know how to handle if in case datafiles
>are fussy. Am I right?
>
>BTW, is there any method to stored archived log in
>raw device for the same purpose?
>
>
>
>P.S. Please remove .NOSPAM when reply by email.
>
>
>
Received on Tue Jul 07 1998 - 04:48:39 CDT