From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: checkpointer: PANIC: could not fsync file: No such file or directory |
Date: | 2019-11-26 04:21:24 |
Message-ID: | 20191126042124.GA3111@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I looked and found a new "hint".
On Tue, Nov 19, 2019 at 05:57:59AM -0600, Justin Pryzby wrote:
> < 2019-11-15 22:16:07.098 EST >PANIC: could not fsync file "base/16491/1731839470.2": No such file or directory
> < 2019-11-15 22:16:08.751 EST >LOG: checkpointer process (PID 27388) was terminated by signal 6: Aborted
An earlier segment of that relation had been opened successfully and was
*still* opened:
$ sudo grep 1731839470 /var/spool/abrt/ccpp-2019-11-15-22:16:08-27388/open_fds
63:/var/lib/pgsql/12/data/base/16491/1731839470
For context:
$ sudo grep / /var/spool/abrt/ccpp-2019-11-15-22:16:08-27388/open_fds |tail -3
61:/var/lib/pgsql/12/data/base/16491/1757077748
62:/var/lib/pgsql/12/data/base/16491/1756223121.2
63:/var/lib/pgsql/12/data/base/16491/1731839470
So this may be an issue only with relations>segment (but, that interpretation
could also be very naive).
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-11-26 04:34:59 | Re: Safeguards against incorrect fd flags for fsync() |
Previous Message | Tatsuro Yamada | 2019-11-26 03:56:48 | Re: progress report for ANALYZE |