Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id EE5DF2E0044 for ; Tue, 22 Apr 2008 06:36:41 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 54245-09 for ; Tue, 22 Apr 2008 06:36:38 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by developer.postgresql.org (Postfix) with ESMTP id EBBA62E0043 for ; Tue, 22 Apr 2008 06:36:37 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n7so3782078wag.5 for ; Tue, 22 Apr 2008 02:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=PTAQ9Bjf7UDQknYWgBbaqTcEuERL93sHEyw1WiCLJYg=; b=e/F4rPuQI/eyTBKQfrXAY0EsWPX9xhr4l0piQEmPodEHSPoGRSOWYtntdAVE8xeOCtKEhy+xH+w1i9DYO2fBnYaFbEL4Ay4MQ9WCRVfFNdksGJXynAbNvKE3TjV/O376zxUqtOgI6smXyeK73m24ZU+WixKmB1l9t/4ehX904MQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=xbXkhji4q5m+ej3BV25rCo2tW3o6RvA0eWOckEnZayprnsKpat4C/MCItHEQQmE5Enmpt0yFQ8Nst6pmBw13gCLCHP7nmGd5cB5gMHBv5gDk5+1qqjXwMucBb4tWAo+7RUY4NaSo+TXTgyYGlPpZRgaNUuInJWInkVtyZ/7cL9Y= Received: by 10.114.14.1 with SMTP id 1mr7180495wan.183.1208856996306; Tue, 22 Apr 2008 02:36:36 -0700 (PDT) Received: by 10.114.95.13 with HTTP; Tue, 22 Apr 2008 02:36:36 -0700 (PDT) Message-ID: <2ca799770804220236u6abf3417qd1eefd3d1cd44196@mail.gmail.com> Date: Tue, 22 Apr 2008 12:36:36 +0300 From: "Mikko Partio" To: "Michael Monnerie" Subject: Re: FATAL: could not open relation xxx: No such file or directory Cc: pgsql-admin@postgresql.org In-Reply-To: <200804221102.59695@zmi.at> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8080_24205063.1208856996301" References: <2ca799770804090647m759b72f9gf2d49b4bf7cc8bdf@mail.gmail.com> <20021.1208445022@sss.pgh.pa.us> <2ca799770804170859t39a5532x4629953e0ec3a600@mail.gmail.com> <200804221102.59695@zmi.at> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/218 X-Sequence-Number: 28982 ------=_Part_8080_24205063.1208856996301 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tue, Apr 22, 2008 at 12:02 PM, Michael Monnerie < michael.monnerie@it-management.at> wrote: > What I had twice (on different customers, once SCSI once SATA) is that a > broken hard disk reports no errors, but delivers different data than > what was written before. Very nasty, as the RAID controller doesn't see > any problem, and destroys even the good harddisks data after the next > write, because the read data is already broken. > How have you recognized such a hard disk? Regards Mikko ------=_Part_8080_24205063.1208856996301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Tue, Apr 22, 2008 at 12:02 PM, Michael Monnerie <michael.monnerie@it-management.at> wrote:
What I had twice (on different customers, once SCSI once SATA) is that a
broken hard disk reports no errors, but delivers different data than
what was written before. Very nasty, as the RAID controller doesn't see
any problem, and destroys even the good harddisks data after the next
write, because the read data is already broken.

How have you recognized such a hard disk?

Regards

Mikko
------=_Part_8080_24205063.1208856996301--