From: | said assemlal <said(dot)assemlal(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: could not fdatasync log file: Input/output error |
Date: | 2017-10-17 23:02:35 |
Message-ID: | CAHtsRKJec-9R0FfqrhrbyyNAo9+JUwTr8i-96spom5Wtp4f7gQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <michael(dot)paquier(at)gmail(dot)com>
wrote:
> On Mon, Oct 16, 2017 at 11:47 PM, said assemlal <said(dot)assemlal(at)gmail(dot)com>
> wrote:
> > Just before we restart the server today, I found only one line as:
> >
> > PANIC: could not fdatasync log file 000000010000017600000083:
> Input/output
> > error
> > the database system is in recovery mode
>
> Ouch. I would not trust this host at this point, this looks like a
> file system or a disk issue. Before doing anything you should stop the
> database, and make a cold copy of the data folder on which you could
> work on if you don't have a live backup. This wiki page is wise on the
> matter:
> http://wiki.postgresql.org/wiki/Corruption
> --
> Michael
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ewen McNeill | 2017-10-18 00:34:22 | Divert triggers on materialized views |
Previous Message | Glenn Pierce | 2017-10-17 22:05:03 | Re: Simple query fail |