Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4ABED2E0053 for ; Mon, 25 Feb 2008 17:19:52 -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 58735-02 for ; Mon, 25 Feb 2008 17:19:49 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by postgresql.org (Postfix) with ESMTP id 8910E2E002C for ; Mon, 25 Feb 2008 17:19:46 -0400 (AST) Received: by wx-out-0506.google.com with SMTP id r21so1656851wxc.28 for ; Mon, 25 Feb 2008 13:19:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=/93GdIGgIBTuxN6IcxonKZykuI33tPzSWspgM/Lpzn4=; b=JTusgfNrKYIftjZMpE3WADWSIqVJ5qSE7abEmLW0heyaxsJ3DNtAxTDDmISEZTT98ASjNJ/QHSS+rKW6hqDNsBjb+uPQ8tdpvAA7sQe7MMbQtE565XaGP1lHpgxiAR59833Fm7BiVr8agD5tbFD2Q1kl2v/w8AWaY6rhzFOT3Z0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=wXAtbSs5fKGLWT8yWju+ih2TRs08axGtZDDBZkDu6KNhtrBhtnUE+abLqEbd5NsMXoPSPEcXbtINZUa782YN5QP2+8XPKegIpIoAw9jm9kVTvx8H6U/8qricXVE4bnotOrpfpaKte6aeC+VtkS1XjDRC2NXd8+tPWcEpVEVtsTc= Received: by 10.70.71.17 with SMTP id t17mr2456840wxa.81.1203974385701; Mon, 25 Feb 2008 13:19:45 -0800 (PST) Received: by 10.70.89.12 with HTTP; Mon, 25 Feb 2008 13:19:45 -0800 (PST) Message-ID: Date: Mon, 25 Feb 2008 15:19:45 -0600 From: "Aaron Bono" To: "Michael Monnerie" Subject: Re: System in Recovery Mode Cc: pgsql-admin@postgresql.org In-Reply-To: <200802252148.47760@zmi.at> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2068_30144702.1203974385690" References: <1203958095.4252.79.camel@ebony.site> <200802252148.47760@zmi.at> X-Google-Sender-Auth: 496520b91d68dbf5 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/325 X-Sequence-Number: 28399 ------=_Part_2068_30144702.1203974385690 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Mon, Feb 25, 2008 at 2:48 PM, Michael Monnerie < michael.monnerie@it-management.at> wrote: > 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. It 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 > broken can cause severe data destroying: We've had this several times > already, with different RAID and drive combinations, SATA and SCSI, > doesn't matter. The symptom was that you write data to the drive, it > says OK, but upon reading you receive other data than you wrote. Even > 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 > inform you that it's a fact that a single broken drive can destroy even > a RAIDs data very nasty. > > mfg zmi > > If I do a pg_dump from this potentially "bad" database and then use the output to do a restore to a new DB on another server, aside from having some data corrupted, would we be able to recover from this problem? If not, what could I do to "fix" the data so the database stops having issues? Thanks! Aaron -- ================================================================== Aaron Bono Aranya Software Technologies, Inc. http://www.aranya.com http://codeelixir.com ================================================================== ------=_Part_2068_30144702.1203974385690 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Mon, Feb 25, 2008 at 2:48 PM, Michael Monnerie <michael.monnerie@it-management.at> wrote:
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.  It 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
broken can cause severe data destroying: We've had this several times
already, with different RAID and drive combinations, SATA and SCSI,
doesn't matter. The symptom was that you write data to the drive, it
says OK, but upon reading you receive other data than you wrote. Even
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
inform you that it's a fact that a single broken drive can destroy even
a RAIDs data very nasty.

mfg zmi


If I do a pg_dump from this potentially "bad" database and then use the output to do a restore to a new DB on another server, aside from having some data corrupted, would we be able to recover from this problem?  If not, what could I do to "fix" the data so the database stops having issues?

Thanks!
Aaron

--
==================================================================
  Aaron Bono
  Aranya Software Technologies, Inc.
  http://www.aranya.com
  http://codeelixir.com
================================================================== ------=_Part_2068_30144702.1203974385690--