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

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:45:51
Message-ID: 1372203951.20761.4.camel@sussancws0025
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 2013-06-25 at 09:46 -0400, Tom Lane wrote:
> "Yuri Levinsky" <yuril(at)celltick(dot)com> writes:
> > PANIC: could not write to log file 81, segment 125 at offset 13959168,
> > length 1392640: No space left on device
>
> 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.
It looks like we assume ENOSPC when errno is not set.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-06-25 23:57:21 Re: Postgres crash? could not write to log file: No space left on device
Previous Message Tom Lane 2013-06-25 16:59:00 Re: Postgres crash? could not write to log file: No spaceleft on device