Skip site navigation (1)
Skip section navigation (2)
How have you recognized such a hard disk?
Regards
Mikko
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 22 Apr 2008 12:36:36 +0300
- Message-id: <2ca799770804220236u6abf3417qd1eefd3d1cd44196(at)mail(dot)gmail(dot)com>
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
- Follow-Ups:
- Re: FATAL: could not open relation xxx: No such file or directory
- From: Michael Monnerie
- Re: FATAL: could not open relation xxx: No such file or directory
- References:
- FATAL: could not open relation xxx: No such file or directory
- From: Mikko Partio
- Re: FATAL: could not open relation xxx: No such file or directory
- From: Tom Lane
- Re: FATAL: could not open relation xxx: No such file or directory
- From: Mikko Partio
- Re: FATAL: could not open relation xxx: No such file or directory
- From: Michael Monnerie
- FATAL: could not open relation xxx: No such file or directory
- Prev by Date: Re: FATAL: could not open relation xxx: No such file or directory
- Next by Date: Re: cannot restore a view after a dump
- Previous by thread: Re: FATAL: could not open relation xxx: No such file or directory
- Next by thread: Re: FATAL: could not open relation xxx: No such file or directory
- Indexes: