Re: [GENERAL] could not fdatasync log file: Input/output error

On Tue, Oct 17, 2017 at 7:13 PM, Michael Paquier wrote: > Note that Peter has also worked on provising Debian packages for the > utility down to 9.4 if I recall correctly, which is nice, but if you > want the heap checks you will need to compile things by youself. We >

Re: [GENERAL] could not fdatasync log file: Input/output error

On Wed, Oct 18, 2017 at 8:02 AM, said assemlal wrote: > Thanks for your response. > > We are currently running postgresql-9.4.14 > I see there are some tools to check if the indexes/pages are not corrupted. > But is there a faster way to check if a PGDATA instance is

Re: [GENERAL] could not fdatasync log file: Input/output error

Thanks for your response. We are currently running postgresql-9.4.14 I see there are some tools to check if the indexes/pages are not corrupted. But is there a faster way to check if a PGDATA instance is clean ? Thanks. On Mon, Oct 16, 2017 at 9:18 PM Michael Paquier

Re: [GENERAL] could not fdatasync log file: Input/output error

On Mon, Oct 16, 2017 at 11:47 PM, said assemlal wrote: > Just before we restart the server today, I found only one line as: > > PANIC: could not fdatasync log file 000101760083: Input/output > error > the database system is in recovery mode Ouch. I would not

Re: [GENERAL] could not fdatasync log file: Input/output error

Just before we restart the server today, I found only one line as: PANIC: could not fdatasync log file 000101760083: Input/output error the database system is in recovery mode On Mon, Oct 16, 2017 at 10:43 AM said assemlal wrote: > Hi, > > The postgresql

[GENERAL] could not fdatasync log file: Input/output error

Hi, The postgresql crashed on friday due to IO errors. It seems that the filesystem puked. PANIC: could not fdatasync log file 000101760077: Input/output error LOG: database system was interrupted; last known up at 2017-10-13 15:26:28 EDT WARNING: terminating connection because of