Re: Postgres crash? could not write to log file: No space left on device

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Yuri Levinsky <yuril(at)celltick(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgres crash? could not write to log file: No space left on device
Date: 2013-06-25 23:57:21
Message-ID: 19878.1372204641@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Tue, 2013-06-25 at 09:46 -0400, Tom Lane wrote:
>> That's definitely telling you it got ENOSPC from a write in
>> $PGDATA/pg_xlog.

> Either that, or write() wrote less than expected but did not set errno.

Good point. I wonder if he's using a filesystem that is capable of
reporting partial writes for other reasons, eg maybe it allows signals
to end writes early. (Though if it is, it's not apparent why such
failures would only be manifesting on the pg_xlog files and not for
anything else.)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2013-06-26 12:14:37 Re: Postgres crash? could not write to log file: No space left on device
Previous Message Jeff Davis 2013-06-25 23:45:51 Re: Postgres crash? could not write to log file: No space left on device