Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5966C2E006D for ; Wed, 20 Feb 2008 17:06:07 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 07057-02 for ; Wed, 20 Feb 2008 17:06:02 -0400 (AST) Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id EF05F2E006C for ; Wed, 20 Feb 2008 17:06:02 -0400 (AST) Received: from mailsrv.i.zmi.at (85-125-129-125.neutorgasse.xdsl-line.inode.at [85.125.129.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mailsrv.i.zmi.at", Issuer "mailsrv.i.zmi.at" (not verified)) by mailsrv1.zmi.at (Postfix) with ESMTP id 3632ABF8 for ; Wed, 20 Feb 2008 22:05:59 +0100 (CET) Received: from saturn.i.zmi.at (saturn.i.zmi.at [10.0.0.2]) by mailsrv.i.zmi.at (Postfix) with ESMTP id 518A5BF2A for ; Wed, 20 Feb 2008 22:05:59 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: Power outage borked things (8.1.10)... Date: Wed, 20 Feb 2008 22:05:58 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <47BBF298.4010108@fastmail.net> <8625.1203523828@sss.pgh.pa.us> In-Reply-To: <8625.1203523828@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2208776.q1fvFFFmpQ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802202205.58380@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/235 X-Sequence-Number: 28309 --nextPart2208776.q1fvFFFmpQ Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mittwoch, 20. Februar 2008 Tom Lane wrote: > 5. Figure out why a simple power failure was able to do this to you, > and fix it. =A0The most likely bet is that your disk drives are lying > about write completion ... see the PG archives for discussion. It could be a caching RAID controller without battery backup unit.=20 Nothing help you in a power failure then, except a good backup. Had this with a customer - no more filesystem after reboot... mfg zmi =2D-=20 // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846 914 666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: www.keyserver.net Key-ID: 1C1209B4 --nextPart2208776.q1fvFFFmpQ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQBHvJY2zhSR9xwSCbQRArvhAKDXuAKbo0e43BShagMccc3rHkAynwCfUefQ 7Ws9Y/OoWg5/1Z8v+2GC8SU= =4HGs -----END PGP SIGNATURE----- --nextPart2208776.q1fvFFFmpQ--