From: Mikko Partio <mpartio@gmail.com>
To: Michael Monnerie <michael.monnerie@it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: FATAL: could not open relation xxx: No such file or directory
Date: Tue, 22 Apr 2008 12:36:36 +0300
Message-ID: <2ca799770804220236u6abf3417qd1eefd3d1cd44196@mail.gmail.com> (raw)
In-Reply-To: <200804221102.59695@zmi.at>
References: <2ca799770804090647m759b72f9gf2d49b4bf7cc8bdf@mail.gmail.com>
<20021.1208445022@sss.pgh.pa.us>
<2ca799770804170859t39a5532x4629953e0ec3a600@mail.gmail.com>
<200804221102.59695@zmi.at>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mpartio@gmail.com, michael.monnerie@it-management.at
Subject: Re: FATAL: could not open relation xxx: No such file or directory
In-Reply-To: <2ca799770804220236u6abf3417qd1eefd3d1cd44196@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox