X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id DE053D1D07E for ; Wed, 7 Apr 2004 19:24:32 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 40043-08 for ; Wed, 7 Apr 2004 19:24:30 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id C42E6D1D065 for ; Wed, 7 Apr 2004 19:24:27 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i37MOUmH005004; Wed, 7 Apr 2004 18:24:30 -0400 (EDT) To: "Tom Bakken" Cc: pgsql-admin@postgresql.org Subject: Re: Out of space In-reply-to: <005301c41ce8$7062a580$770e9dc7@agwest.one.usda.gov> References: <005301c41ce8$7062a580$770e9dc7@agwest.one.usda.gov> Comments: In-reply-to "Tom Bakken" message dated "Wed, 07 Apr 2004 16:36:51 -0500" Date: Wed, 07 Apr 2004 18:24:30 -0400 Message-ID: <5003.1081376670@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/131 X-Sequence-Number: 13104 "Tom Bakken" 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