At 07:42 PM 6/11/2006 +0200, Florian Weimer wrote:
We recently had a partially failed disk in a RAID-1 configuration
which did not perform a write operation as requested. Consequently,
What RAID1 config/hardware/software was this?
Could be good to know...
Regards,
Link.
On Sun, Jun 11, 2006 at 07:42:55PM +0200, Florian Weimer wrote:
We recently had a partially failed disk in a RAID-1 configuration
which did not perform a write operation as requested. Consequently,
the mirrored disks had different contents, and the file which
contained the block switched
* Lincoln Yeoh:
At 07:42 PM 6/11/2006 +0200, Florian Weimer wrote:
We recently had a partially failed disk in a RAID-1 configuration
which did not perform a write operation as requested. Consequently,
What RAID1 config/hardware/software was this?
I would expect that any RAID-1 controller
* Jim C. Nasby:
Anyway, how would be the chances for PostgreSQL to detect such a
corruption on a heap or index data file? It's typically hard to
detect this at the application level, so I don't expect wonders. I'm
just curious if using PostgreSQL would have helped to catch this
sooner.
I
On Mon, Jun 12, 2006 at 07:55:22PM +0200, Florian Weimer wrote:
* Jim C. Nasby:
Anyway, how would be the chances for PostgreSQL to detect such a
corruption on a heap or index data file? It's typically hard to
detect this at the application level, so I don't expect wonders. I'm
just
We recently had a partially failed disk in a RAID-1 configuration
which did not perform a write operation as requested. Consequently,
the mirrored disks had different contents, and the file which
contained the block switched randomly between two copies, depending on
which disk had been read. (In
Florian Weimer [EMAIL PROTECTED] wrote
Anyway, how would be the chances for PostgreSQL to detect such a
corruption on a heap or index data file? It's typically hard to
detect this at the application level, so I don't expect wonders. I'm
just curious if using PostgreSQL would have helped to
