Re: [GENERAL] could not fdatasync log file: Input/output error
| От | said assemlal |
|---|---|
| Тема | Re: [GENERAL] could not fdatasync log file: Input/output error |
| Дата | |
| Msg-id | CAHtsRKJec-9R0FfqrhrbyyNAo9+JUwTr8i-96spom5Wtp4f7gQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] could not fdatasync log file: Input/output error (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: [GENERAL] could not fdatasync log file: Input/output error
|
| Список | 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.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 ?
On Mon, Oct 16, 2017 at 9:18 PM Michael Paquier <michael.paquier@gmail.com> wrote:
On Mon, Oct 16, 2017 at 11:47 PM, said assemlal <said.assemlal@gmail.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
В списке pgsql-general по дате отправления: