Re: could not fdatasync log file: Input/output error

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: said assemlal <said(dot)assemlal(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 01:18:21
Message-ID: CAB7nPqSUt0rq62RQz2ZH-t4nkOQYNocqpbP50r6x+jyninXh6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2017-10-17 04:54:54 Re: wal_retrieve_retry_interval
Previous Message Tatsuo Ishii 2017-10-17 01:17:39 PGConf.ASIA and VISA