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

From: said assemlal <said(dot)assemlal(at)gmail(dot)com>
To: "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-16 14:47:58
Message-ID: CAHtsRK+Oz1tZiZmxNNRrgT4W600GpQVWeWv1nHQpemE5YiZZbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

On Mon, Oct 16, 2017 at 10:43 AM said assemlal <said(dot)assemlal(at)gmail(dot)com>
wrote:

> Hi,
>
> The postgresql crashed on friday due to IO errors. It seems that the
> filesystem puked.
>
> PANIC: could not fdatasync log file 000000010000017600000077: Input/output
> error
> LOG: database system was interrupted; last known up at 2017-10-13 15:26:28
> EDT
> WARNING: terminating connection because of crash of another server process
> FATAL: the database system is in recovery mode
>
> Some errors from the kernel given by the sysadmin:
>
> Buffer I/O error on device dm-3, logical block 2900794
> lost page write due to I/O error on dm-3
> Buffer I/O error on device dm-3, logical block 2900795
> lost page write due to I/O error on dm-3
> Buffer I/O error on device dm-3, logical block 2900796
> lost page write due to I/O error on dm-3
> Buffer I/O error on device dm-3, logical block 2900797
> lost page write due to I/O error on dm-3
>
> So we have restarted the server, everything seems to be fine. Should I
> perform other tests ? Or Should I use a backup to restore the database ?
>
> Thanks for your advice.
> Saïd
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Osahon Oduware 2017-10-16 14:54:35 Re: Using Substitution Variables In PostgreSQL
Previous Message said assemlal 2017-10-16 14:43:05 could not fdatasync log file: Input/output error