Re: FATAL: could not open relation xxx: No such file or directory

------=_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@[EMAIL PROTECTED]
> wrote:

> What I had twice (on different customers, once SCSI once SATA) is that a
> broken hard disk re****ts 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

<br><br><div class="gmail_quote">On Tue, Apr 22, 2008 at 12:02 PM, Michael
Monnerie &lt;<a
href="mailto:michael.monnerie@[EMAIL PROTECTED]
">michael.monnerie@[EMAIL PROTECTED]
>&gt;
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What I had twice (on different customers, once SCSI once SATA) is that
a<br>
broken hard disk re****ts no errors, but delivers different data than<br>
what was written before. Very nasty, as the RAID controller doesn&#39;t
see<br>
any problem, and destroys even the good harddisks data after the next<br>
write, because the read data is already broken.<br>
</blockquote></div><br>How have you recognized such a hard
disk?<br><br>Regards<br><br>Mikko<br>

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