Mitch Vincent wrote:
> > Well from my experience the reason systems crash are hardware failuers
> > or power failuers. If your hard disk crashes it won't make any differnce
> > whether you fsync was on off, you are reloading from backups unless you
> > are running araid system. If the system is a mission critical one then
> > I'd assume you would have some sort of UPS or alternate power supply..
> > it would seem that the chances of a hardware failure is minimal leaving
> > the fsync off is probably pretty safe.
>
> ... or someone tripping over a power cord to the UPS or someone hitting the
> reset button on the machine thinking it was a different machine -- the thing
> is that with fsync() off, even someone hitting the reset button on the
> machine and rebooting it could cause severe database corruption even though
> the rest of your system is virtually unharmed with a spontaneous reboot
> (minus the running of fsck or other utilities to verify the drive's
> integrity )..
>
> I agree that the chances of it happening are probably low but if the data is
> mission critical then I wouldn't even take a small chance with corruption..
>
> Just be careful!
>
> -Mitch
If your system is mission critical, then you lock it away in a separate
room,
and take care that only the people who really need access have keys.
This
should not be more than three persons. And since this is Linux, once the
system is up and running, all administration can be done via telnet.
The only reason that you enter the room is to change backup-tapes (or
maybe backups can be taken remotely) and to do hardware maintenance.
Jurgen