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

From: "Mikko Partio" <mpartio(at)gmail(dot)com>
To: "Michael Monnerie" <michael(dot)monnerie(at)it-management(dot)at>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: FATAL: could not open relation xxx: No such file or directory
Date: 2008-04-22 09:36:36
Message-ID: 2ca799770804220236u6abf3417qd1eefd3d1cd44196@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Apr 22, 2008 at 12:02 PM, Michael Monnerie <
michael(dot)monnerie(at)it-management(dot)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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Marc Cousin 2008-04-22 09:45:02 Re: cannot restore a view after a dump
Previous Message Michael Monnerie 2008-04-22 09:02:59 Re: FATAL: could not open relation xxx: No such file or directory