pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mauri Sahlberg <Mauri.Sahlberg@claymountain.com>
To: Ian Westmacott <ianw@intellivid.com>
Cc: pgsql-admin@postgresql.org
Cc: theporro@saunalahti.fi
Cc: peikko@claymountain.com
Subject: Re: Help desperately needed: reoccurring invalid page
Date: Fri, 29 Apr 2005 09:38:16 +0300
Message-ID: <4271D658.8050402@claymountain.com> (raw)
In-Reply-To: <1114693098.13031.16.camel@spectre.intellivid.com>
References: <42708252.7070003@claymountain.com>
	<1114693098.13031.16.camel@spectre.intellivid.com>

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.




view thread (3+ messages)

Message-ID: <4271D658.8050402@claymountain.com>
Permalink:  ../4271D658.8050402@claymountain.com/
Also on:    postgresql.org/message-id/4271D658.8050402@claymountain.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Mauri.Sahlberg@claymountain.com, ianw@intellivid.com, theporro@saunalahti.fi, peikko@claymountain.com
  Subject: Re: Help desperately needed: reoccurring invalid page
  In-Reply-To: <4271D658.8050402@claymountain.com>
  References: <42708252.7070003@claymountain.com> <1114693098.13031.16.camel@spectre.intellivid.com> <4271D658.8050402@claymountain.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox