pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Bakken <tom.bakken@tx.usda.gov>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Out of space
Date: Thu, 8 Apr 2004 08:10:25 -0500
Message-ID: <001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov> (raw)
In-Reply-To: <5003.1081376670@sss.pgh.pa.us>

Tom,

I'm not sure how to check about the postgres user disk space limit issue.  I
tried storing a rather large file on the postgres partition as the postgres
user and had no problem.  I'm more suspicious of the file stored in:

[root@linux04 data]# ls -l /var/lib/pgsql/data/pg_xlog/
total 16404
-rw-------    1 postgres postgres 16777216 Apr  7 12:14 000000010000001E

Is it typical?  It doesn't look it.

Anyway, I've got plenty of space but am unsure of the next step.

Tom Bakken
Information Resource Manager
Texas USDA, Rural Development 

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Wednesday, April 07, 2004 5:25 PM
To: Tom Bakken
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Out of space 


"Tom Bakken" <tom.bakken@tx.usda.gov> writes:
> OK, it's truncated and now I've got plenty of space, but it's still
> complaining that it can't find the xlogtemp.1405:

> FATAL 2:  ZeroFill(/var/lib/pgsql/data/pg_xlog/xlogtemp.1405) failed: No
> such file or directory

I think the "no such file" errno is probably actively misleading.  I
took another look at the CVS logs and realized that in 7.1.2, there is
no guarantee that that message actually reflects the cause of the write
failure --- if write() indicates it couldn't write all the bytes, but
does not set errno, then the reported errno will be left over from the
last failed operation.  We had patched this by 7.1.3, which is the
version I was looking at locally.  Since ENOENT can't be returned by
write() AFAIK, it seems certain that this is indeed a leftover errno
setting.

In short, I still think you are running into some kind of
out-of-disk-space failure.  I'm not sure what, but you might look to
whether you've exceeded the postgres user's disk space quota, or
anything along that line.  Keep in mind also that an unprivileged user
account normally can't fill the disk as full as root can.

			regards, tom lane

Attachments:

Tom.Bakken@tx.usda.gov.vcf (text/x-vcard, 446B) download BEGIN:VCARD VERSION:2.1 N:Bakken;Tom FN:Tom.Bakken@tx.usda.gov ORG:Texas State Office TEL;WORK;VOICE:(254) 742-9726 TEL;WORK;FAX:(254) 742-9709 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;101 South Main=0D=0ASuite 102;Temple;TX;76502;United States of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:101 South Main=0D=0ASuite 102=0D=0ATemple, TX 76502=0D=0AUnited States of Am= erica EMAIL;PREF;INTERNET:Tom.Bakken@tx.usda.gov REV:20040301T143942Z END:VCARD

view thread (16+ messages)  latest in thread

Message-ID: <001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov>
Permalink:  ../001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov/
Also on:    postgresql.org/message-id/001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tom.bakken@tx.usda.gov, tgl@sss.pgh.pa.us
  Subject: Re: Out of space
  In-Reply-To: <001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov>
  References: <5003.1081376670@sss.pgh.pa.us> <001201c41d6a$db7bd080$770e9dc7@agwest.one.usda.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox