A non-journaled file system would need to run a check to see if everything is ok. This could take a long time on a big drive.
How could you even tell if something was wrong on a raw partition? There isn't a whole lot of metadata to check for problems against like there is in a filesystem. It's up to the application to recover from errors.
Raw partitions used to be used for performance, not for safety. Hardware has gotten so fast, that there really is no difference in performance between a file system and a raw partition. Hardware fails, software has bugs.
On Mar 30, 2005, at 1:09 PM, Florin Andrei wrote:
Wouldn't raw partitions fail less often if the power is yanked, just because there are fewer components to fail? I mean, if the database is on top of a FS, it's the database and the FS that can fail. On a raw partition, it's just the database. Or am i missing something?
-- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
