Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3ADF42E003E for ; Mon, 25 Feb 2008 17:09:29 -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 54318-08 for ; Mon, 25 Feb 2008 17:09:24 -0400 (AST) X-Greylist: delayed 00:20:33.185954 by SQLgrey-1.7.5 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by postgresql.org (Postfix) with ESMTP id 288572E002F for ; Mon, 25 Feb 2008 17:09:23 -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 C12B9CD2 for ; Mon, 25 Feb 2008 21:48:47 +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 AE4D8BF16 for ; Mon, 25 Feb 2008 21:49:01 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: System in Recovery Mode Date: Mon, 25 Feb 2008 21:48:47 +0100 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) References: <1203958095.4252.79.camel@ebony.site> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2564717.0AQ9N7xClX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200802252148.47760@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/324 X-Sequence-Number: 28398 --nextPart2564717.0AQ9N7xClX Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Montag, 25. Februar 2008 Aaron Bono wrote: > We did have a hard drive problem (errors on the drive) in the past > and they had to swap out a drive. =A0It is a RAID configuration so no > backup/restore was necessary. Even with a RAID system, a broken hard drive that doesn't show that it's=20 broken can cause severe data destroying: We've had this several times=20 already, with different RAID and drive combinations, SATA and SCSI,=20 doesn't matter. The symptom was that you write data to the drive, it=20 says OK, but upon reading you receive other data than you wrote. Even=20 RAID 1/5/6 doesn't help you here. Doesn't mean you have the same, but from what you wrote I just wanted to=20 inform you that it's a fact that a single broken drive can destroy even=20 a RAIDs data very nasty. 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 --nextPart2564717.0AQ9N7xClX 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) iD8DBQBHwymvzhSR9xwSCbQRAuV4AKDVDXsEVvOkqgjx/OiX0PWvAfXy5QCg3Lyy safHvSRH5YPnX7TFEAgoN+s= =6VMo -----END PGP SIGNATURE----- --nextPart2564717.0AQ9N7xClX--