Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id A436D6327E7 for ; Mon, 26 Jul 2010 22:34:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 90201-05 for ; Tue, 27 Jul 2010 01:33:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 05A5D62DB89 for ; Mon, 26 Jul 2010 22:33:56 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o6R1Xqsv026276; Mon, 26 Jul 2010 21:33:52 -0400 (EDT) To: Alex Hunsaker cc: ibarg@noao.edu, pgsql-admin@postgresql.org Subject: Re: postgresql-server-8.4.4-1PGDG.el5 - ERROR: could not write block 503414 of temporary file: No space le, ft on device In-reply-to: References: <4C4E05C8.9090702@noao.edu> Comments: In-reply-to Alex Hunsaker message dated "Mon, 26 Jul 2010 17:09:38 -0600" Date: Mon, 26 Jul 2010 21:33:52 -0400 Message-ID: <26275.1280194432@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201007/183 X-Sequence-Number: 35202 Alex Hunsaker writes: > On Mon, Jul 26, 2010 at 16:01, Irene Barg wrote: > 2010-07-26 11:33:33 MST system_admin metadataERROR:  could not write block > 503414 of temporary file: No space le > ft on device > 2010-07-26 11:33:33 MST system_admin metadataHINT:  Perhaps out of disk > space? > Ok so it looks like this is on your / (sda3) partition that only has > 1.7G free. Its entirely possible that you have some query that needs > to write more than that in tmp files. "Block 503414" is a red flag here --- that means that this temp file alone required 503414 * 8K = nearly 4Gb. I suspect /var/lib/pgsql has been symlinked someplace else, as the root device has clearly not got anything close to that much free space. It's quite possible that the query involved multiple temp files, though, so maybe one of the other partitions is getting filled. regards, tom lane