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 47EB452A38 for ; Fri, 29 Apr 2005 03:38:27 -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 41600-02 for ; Fri, 29 Apr 2005 06:38:17 +0000 (GMT) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by svr1.postgresql.org (Postfix) with ESMTP id 063555370E for ; Fri, 29 Apr 2005 03:38:16 -0300 (ADT) Received: from [192.168.105.219] (unknown [195.197.242.66]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id 44720BD41F; Fri, 29 Apr 2005 09:38:16 +0300 (EEST) Message-ID: <4271D658.8050402@claymountain.com> Date: Fri, 29 Apr 2005 09:38:16 +0300 From: Mauri Sahlberg User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Westmacott Cc: pgsql-admin@postgresql.org, theporro@saunalahti.fi, peikko@claymountain.com Subject: Re: Help desperately needed: reoccurring invalid page References: <42708252.7070003@claymountain.com> <1114693098.13031.16.camel@spectre.intellivid.com> In-Reply-To: <1114693098.13031.16.camel@spectre.intellivid.com> X-Enigmail-Version: 0.90.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 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/400 X-Sequence-Number: 17413 Hi, Ian Westmacott wrote: >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). > > Uh. As our cheap server is a virtual machine under a virtuozzo (http://www.sw-soft.com/products/virtuozzo/) I have no control over what kernel to run or what filesystem to use. Nor has there been frequent reboots. I have restarted the virtual server twice in 4 months and the provider has done it once since production started. But as it might still be a filesystem problem (vzfs) I should try to find documentation on vzfs to see if I can do something to increase its "reliability" or if the provider can do that. The client side did fail very frequently for a while due non mature w-lan card driver and that might have caused the corruption that did not got fixed properly by my inept attempts and still lurks around. >- 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). > > > Thanks I will try that. >- We have not found a way around the missing log file > problem. This appears to end up locking some rows > forever. > > It seems to me that the best course for action for us would be: Zeroing damaged pages. Dump every database excluding templates. Shutdown. Remove provider's postgresql-rpms and install the latest rpms on 7-series of Postgresql from Fedora legacy/pgfoundry. Restore databases. Manually merge changes from older backups that got zeroed. Upgrade client-side to the same version of postgresql as the server side. Recompile libraries and applications. Startup. Backup. Increase frequenzy of backups and hope for the best.