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 58A3053B28 for ; Thu, 28 Apr 2005 09:58:18 -0300 (ADT) 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 00254-08 for ; Thu, 28 Apr 2005 12:58:17 +0000 (GMT) Received: from mailhost.intellivid.com (mailhost.intellivid.com [64.32.200.11]) by svr1.postgresql.org (Postfix) with ESMTP id DAB6353B4E for ; Thu, 28 Apr 2005 09:58:16 -0300 (ADT) Received: from [192.168.2.68] (spectre.intellivid.com [192.168.2.68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by newmail.intellivid.com (Postfix) with ESMTP id CF4CCF1817E; Thu, 28 Apr 2005 08:58:18 -0400 (EDT) Subject: Re: Help desperately needed: reoccurring invalid page From: Ian Westmacott To: Mauri Sahlberg Cc: pgsql-admin@postgresql.org, peikko@claymountain.com, PoRRo In-Reply-To: <42708252.7070003@claymountain.com> References: <42708252.7070003@claymountain.com> Content-Type: text/plain Message-Id: <1114693098.13031.16.camel@spectre.intellivid.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 28 Apr 2005 08:58:18 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/395 X-Sequence-Number: 17408 Mauri, I'm no expert but I can tell you what I know. We have experienced this same problem, and I asked a similar question not too long ago. - This is probably due to some sort of I/O problem. In our case, it occurs very frequently on reboots, and it appears to be related to dirty buffers not being flushed out when the partition is unmounted. Look into a newer kernel, and/or newer/different filesystem (we have seen this in various flavors of the 2.4.6 kernel with XFS, JFS and EXT3). - If you have invalid page headers, you should take a look at the run-time parameter zero_damaged_pages. You can use this to fix up a table (losing the data on the bad pages). - We have not found a way around the missing log file problem. This appears to end up locking some rows forever. Others on this list may be able to tell you about tools for examining/fixing corrupt tables and log files. --Ian