| From: | Phil Hildebrand <phil(dot)hildebrand(at)moz(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |
| Date: | 2019-01-02 15:20:23 |
| Message-ID: | CAKk9fdXNbwXb4uH2KDs+2bvdkAWTgU53_EqWxOTzJ5dOoFWTKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thanks!
On Wed, Jan 2, 2019 at 5:53 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Tue, Jan 01, 2019 at 12:13:05AM -0800, Phil Hildebrand wrote:
> > That said, these are VMs running on ESX hosts with SSD, so it's
> > certainly possible. We'll check the hosts as well.
>
> You may have been bitten by a recent bug on ESX side. Looking around
> there has been a release 2 months ago which fixes an issue with
> similar symptoms:
> https://docs.vmware.com/en/VMware-vSphere/6.5/rn/esxi650-201810002.html
>
> I am referring to this one in particular:
> "PR 2209189: Heavy I/Os issued to a snapshot virtual machine using the
> SEsparse format might cause guest OS file system inconsistencies."
>
> And in this case this could be referring to 4kB blocks written where
> they should not.
> --
> Michael
>
--
Phil Hildebrand
Sr. DBE @ Moz
206.696.3413
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexey Bashtanov | 2019-01-02 17:33:12 | Is temporary functions feature official/supported? Found some issues with it. |
| Previous Message | Michael Paquier | 2019-01-02 12:52:53 | Re: BUG #15570: Vacuum analyze ERROR: MultiXactId XXXX has not been created yet -- apparent wraparound |