On Fri, 17 Jun 2005 13:57:26 -0500 David Sze <[EMAIL PROTECTED]> wrote:
> I'm not sure filesystem consistency alone is "good enough". Say your > bank's database crashes right after you make a deposit. When it comes > back up it's consistent, but only up to 5 minutes before the crash due > to the async mount. > > For this type of application, something in the system has to be keeping > a "journal" on a sync mount in order for recovery to be both consistent > and correct. For that critical an application the transaction should be stored in multiple physically separated locations and confirmed by the two faced kermit\w\w\w two phase commit protocol. Said implementation had better have the correct disaster restart protocol implemented too. -- C:>WIN | Directable Mirror Arrays The computer obeys and wins. | A better way to focus the sun You lose and Bill collects. | licences available see | http://www.sohara.org/ _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"