X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A7E573A2CB4 for ; Sat, 15 Jan 2005 18:01:57 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 37276-01 for ; Sat, 15 Jan 2005 18:01:41 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 158423A2CCD for ; Sat, 15 Jan 2005 18:01:18 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0FI1HYo010234; Sat, 15 Jan 2005 13:01:18 -0500 (EST) To: "Sander Steffann" Cc: pgsql-admin@postgresql.org Subject: Re: Less available diskspace after crashed CLUSTER In-reply-to: <003201c4fb14$b7377840$64c8a8c0@balefirehome> References: <003201c4fb14$b7377840$64c8a8c0@balefirehome> Comments: In-reply-to "Sander Steffann" message dated "Sat, 15 Jan 2005 16:13:05 +0100" Date: Sat, 15 Jan 2005 13:01:17 -0500 Message-ID: <10233.1105812077@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/164 X-Sequence-Number: 16023 "Sander Steffann" writes: > 2005-01-15 15:17:46 [30605] PANIC: PANIC: could not write to file > "/var/lib/pgsql/data/pg_xlog/xlogtemp.30605": Geen ruimte over op apparaat > STATEMENT: CLUSTER; Hmm. I wonder why we have XLogFileInit forcing a PANIC for this. At one time it was called only from critical sections and so the error would become a panic anyway, but that's not true anymore... > The database is running nice again, but I have the feeling I lost some > diskspace... I suspected a temp file, so I stopped the postmaster, looked in > /var/lib/pgsql/data/base/17142/pgsql_tmp, found one file and deleted it. But > now I still have 1G less available diskspace than before the CLUSTER. > Where should I look next? I would like the diskspace back :-) I'm guessing that the new table/index files created during the CLUSTER didn't get released after the PANIC. Look for files that are not referenced by any relfilenode value in pg_class. Don't forget that there may be multiple sections (filenode.1, etc). See http://developer.postgresql.org/docs/postgres/storage.html (which is for 8.0, but everything except the material on tablespaces applies to 7.4). Also, did you get rid of the xlog temp file mentioned in the message? regards, tom lane