Hello, Linux People!Because if your filesystem is not journaled, a crash has no way of assuring the consistancy of the files on it. If the database's journal is consequenctly corrupted, nothing in the world will help you.
after short consultation, i have come to this conclusion about which filesystem i should use on my database box (or server) the winner is: ex2 linux extended filesystem, yes, lassies & lads
- "why not ext3/Reiser's ?" - "because journalling is already implemented in the DBMS." - "why not jfs then ? - "it is too young, my friends + journalling..." - "why not xfs , it is so ... juicy ? - "it is too resource demanding (i have p2 670MHz + 256 MB )"
if somebody thinks otherwise, please tell me why!
thank you.
Ideally, you will have a database that can use the file system's journal, instead of keeping it's own. Failing that, use double journal. I don't think it's a good idea to let go of the filesystem's recovery.
Shachar
-- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
