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

From: "Yuri Levinsky" <yuril(at)celltick(dot)com>
To: "Andres Freund" <andres(at)2ndquadrant(dot)com>, "Greg Stark" <stark(at)mit(dot)edu>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Postgres crash? could not write to log file: No spaceleft on device
Date: 2013-06-26 13:03:16
Message-ID: B72526FA2066E344AFD09734A487318103E92B9C@falcon1.celltick.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Sorry for delay, the email somehow went into junk mails folder. I
didn't compiled Postgres, we downloaded the already compiled version for
SUN Solaris 10 64 bit. The same version is working fine on other
installations. On this specific installation we got "buggy kernel" error
during massive data load (copy) from Informix. As result we added "noac"
flag to NFS that looking on NetApp storage. The "noac" means disable NFS
caching, the problem disappeared despite multiple and instant reproduces
before. Unfortunately after site went up we started to see DB reboots
for 2 days. I disabled pg_dump with tar option, that somehow filled up
by 100% the /var directory and freed it after failure. I limited the
temp storage per session as well. Unfortunately I lost the connection to
the site and unable to check today if it helped or not.

Sincerely yours,

Yuri Levinsky, DBA
Celltick Technologies Ltd., 32 Maskit St., Herzliya 46733, Israel
Mobile: +972 54 6107703, Office: +972 9 9710239; Fax: +972 9 9710222

-----Original Message-----
From: Andres Freund [mailto:andres(at)2ndquadrant(dot)com]
Sent: Wednesday, June 26, 2013 3:21 PM
To: Greg Stark
Cc: Tom Lane; Jeff Davis; Yuri Levinsky; pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] Postgres crash? could not write to log file: No
spaceleft on device

On 2013-06-26 13:14:37 +0100, Greg Stark wrote:
> On Wed, Jun 26, 2013 at 12:57 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > (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.)
>
> Well data files are only ever written to in 8k chunks. Maybe these
> errors are only occuring on >8k xlog records such as records with
> multiple full page images. I'm not sure how much we write for other
> types of files but they won't be written to as frequently as xlog or
> data files and might not cause errors that are as noticeable.

We only write xlog in XLOG_BLCKSZ units - which is 8kb by default as
well...

Yuri, have you compiled postgres with nonstandard configure or
pg_config_manual.h settings?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

This mail was received via Mail-SeCure System.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2013-06-26 13:04:00 Re: Postgres crash? could not write to log file: No space left on device
Previous Message Heikki Linnakangas 2013-06-26 12:40:08 Re: Postgres crash? could not write to log file: No space left on device