| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Ioana Danes <ioanadanes(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupted Data ? |
| Date: | 2016-08-13 08:49:56 |
| Message-ID: | CA+bJJbyVijaC1C_-fSqpjc-GU_f=kc5ei_dg5SiqDkT3Vnvthw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Adrian:
On Fri, Aug 12, 2016 at 9:01 PM, Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com> wrote:
> "Specially if this happens, you may have some slightly bad disks/ram/
> leading to this kind of problems."
>
> Trying to reconcile that with all the physical machine 1 VMs sharing the
> same RAM and physical disk, but the error only occurring on db3.
>
> Is the VM hosting db3 setup different from the VMs 1 & 2?
They probably share the disk, bus, ram and disk controllers, but they
surely do not share the disk SECTORS. "Weak" ( nearly failing ) tracks
can give this kind of problems ( although the disk CRC should catch
all odd number of bit errors , but with VMs in the mix who knows where
the messages could end up ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Olarte | 2016-08-13 08:57:18 | Re: Any reasons for 'DO' statement not returning result? |
| Previous Message | Patrick B | 2016-08-13 06:50:14 | Re: PK Index - Removal |