Date: Fri, 18 Dec 2009 11:12:04 -0700 From: Chad Perrin <perrin@apotheon.com> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD is too filesystem errors sensitive Message-ID: <20091218181204.GB98208@guilt.hydra> In-Reply-To: <4B1E2D40.9060900@sprinthost.ru> References: <4B1DF953.4050504@sprinthost.ru> <hfl7v5$f9j$1@ger.gmane.org> <4B1E2D40.9060900@sprinthost.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 08, 2009 at 01:41:04PM +0300, cronfy wrote: >=20 > After panic data *is* getting corrupted anyway - MySQL tables that were= =20 > open are broken, soft-updates are unsync'ed etc etc. By the way, you might want to look into using a DBMS that (unlike MySQL) doesn't hose up open tables because of a power failure or kernel panic. Choose something ACID-compliant like PostgreSQL if you fear data loss. There are evidently a couple of storage engines for MySQL that also provide much the same safety for your data, too, but you can't just settle for the default and hope that's good enough. If it's an option for you, you may want to look into disabling soft updates as well so that you don't have to just hope that everything gets synced before the end of the world. Depending on your usage, however, this might result in unacceptably poor performance. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAksrxfQACgkQ9mn/Pj01uKWe9QCcCxVEBjcfz8IxVKNjOCFODnQ5 Vw8AnjiMdYeNy4nbAHzE8WH+Rp1FL6G2 =YTbY -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091218181204.GB98208>