From: | Rocco Zanni <rocco(dot)zanni(at)spreaker(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange crash logs |
Date: | 2012-05-09 15:15:51 |
Message-ID: | FF4532F7-9F7A-4FA5-8375-75C37C95FBE9@spreaker.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Tom,
we've discovered more informations in the meanwhile.
It seems that a bug in our backup tools caused a freeze in the
database filesystem. The tool was stucked inside an xfs_freeze for a
several minutes and caused the kernel to terminate processes locked
waiting for write lock. One of this processes was postgresql.
I don't believe that was an issue on postgres-side.
Bye,
Rocco
---
Rocco Zanni
rocco(dot)zanni(at)spreaker(dot)com
http://www.spreaker.com
Il giorno 09/mag/12, alle ore 17:08, Tom Lane ha scritto:
> Rocco Zanni <rocco(dot)zanni(at)spreaker(dot)com> writes:
>> someone can help me understanding what happened in this crash logs?
>> http://pastebin.com/0ruR4egm
>
> What was happening *before* the lines you showed?
>
> The information there seems to indicate that something got stuck while
> holding the ProcStructLock, but there's no way to tell what or why
> from
> this much info.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Samba | 2012-05-09 16:00:11 | Re: Issue with rsync based incremental backup : postgres: startup process waiting for 0000000100000001000000D2 |
Previous Message | Randy Johnson | 2012-05-09 15:11:23 | config file question between versions 7.4 - 9.1 |