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 30940D1D90E for ; Fri, 6 Feb 2004 21:01:28 +0000 (GMT) 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 97789-02 for ; Fri, 6 Feb 2004 17:01:26 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 83B2BD1D767 for ; Fri, 6 Feb 2004 17:01:24 -0400 (AST) 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 i16L1PRA012369; Fri, 6 Feb 2004 16:01:25 -0500 (EST) To: kaolin fire Cc: pgsql-admin@postgresql.org Subject: Re: FATAL 2: (pg_clog ... no such file or directory) In-reply-to: <4536F22E-58CB-11D8-ABC6-000A957FF036@tentacle.net> References: <20030904125947.A3F73D1B89A@svr1.postgresql.org> <4536F22E-58CB-11D8-ABC6-000A957FF036@tentacle.net> Comments: In-reply-to kaolin fire message dated "Fri, 06 Feb 2004 09:38:27 -0800" Date: Fri, 06 Feb 2004 16:01:25 -0500 Message-ID: <12368.1076101285@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/98 X-Sequence-Number: 12272 kaolin fire writes: > Where would I go to start tracking down recurring error messages of the > sort: > FATAL 2: open of /usr/local/pgsql/data/pg_clog/06F7 failed: No such > file or directory > FATAL 2: open of /usr/local/pgsql/data/pg_clog/0707 failed: No such > file or directory > 06F7 and 0707 do not exist. Currently just looks like it goes from > 0000 (May 14 2002) to 004F (Feb 6 2004, and counting). Given those facts, you have corrupt data --- specifically, a wildly out-of-range transaction number in some tuple header, causing the tuple validity checker to try to fetch a nonexistent page of the CLOG. The odds are good that the corruption extends further than just the one field; that just happens to be the one that gets checked first. There are discussions in the mailing list archives about how to locate and clean up corrupted data. It's a pretty messy process but you can usually get back everything except the rows on the particular corrupted page (I'm optimistically assuming there's only one). Looking for threads mentioning pg_filedump might be the quickest way to find info. regards, tom lane