Subject Journaled file systems
Author Rick Debay
[also posted to comp.os.linux.setup and alt.linux.suse]

I'm installing Suse 11 for a database server, and need to set up the
data file
system to be as reliable as possible.
It's going to be ext3 mounted with the sync flag. I was looking at the
journaling options, and was wondering if journaling the data was worth
it. From
a data safety perspective, the data is on the disk whether it writes it
to the
data journal or directly to the file. While a partial write to a file
would
normally cause problems, in a transactional database the incomplete
writes would
just be rolled back.

I can see a performance advantage if the journal is on different
hardware, so as
to handle burst conditions.

Am I missing something? Does anyone have any recommendations?

-- following text not posted to usenet --

Will Firebird have a problem if there was a partial write to the
database file, and the OS did NOT report that the write was complete?

Secondly, am I correct in assuming that Firebird's temporary files do
not need any special precautions such as making them synchronous or
preserving them across reboots?

Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.