| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Benedikt Grundmann <bgrundmann(at)janestreet(dot)com> |
| Cc: | PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>, David Powers <dpowers(at)janestreet(dot)com> |
| Subject: | Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM) |
| Date: | 2013-05-15 06:24:03 |
| Message-ID: | 51932A03.3070908@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14.05.2013 23:47, Benedikt Grundmann wrote:
> The only thing that is *new* is that we took the snapshot from the
> streaming replica. So again my best guess as of now is that if the
> database crashes while it is in streaming standby a invalid disk state can
> result during during the following startup (in rare and as of now unclear
> circumstances).
A bug is certainly possible. There isn't much detail here to debug with,
I'm afraid. Can you share the full logs on all three systems? I'm
particularly interest
> You seem to be quite convinced that it must be LVM can you elaborate why?
Well, you said that there was a file in the original filesystem, but not
in the snapshot. If you didn't do anything in between, then surely the
snapshot is broken, if it skipped a file. Or was the file created in the
original filesystem after the snapshot was taken? You probably left out
some crucial details on how exactly the snapshot and rsync are
performed. Can you share the scripts you're using?
Can you reproduce this problem with a new snapshot? Do you still have
the failed snapshot unchanged?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2013-05-15 06:42:02 | plperl segfault in plperl_trusted_init() on kfreebsd |
| Previous Message | Amit Kapila | 2013-05-15 05:56:40 | Re: streaming replication, "frozen snapshot backup on it" and missing relfile (postgres 9.2.3 on xfs + LVM) |