Skip site navigation (1) Skip section navigation (2)

Re: Power outage borked things (8.1.10)...

From: Hannes Dorbath <light(at)theendofthetunnel(dot)de>
To: Michael Monnerie <michael(dot)monnerie(at)it-management(dot)at>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Power outage borked things (8.1.10)...
Date: 2008-02-21 22:00:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
Michael Monnerie wrote:
> On Mittwoch, 20. Februar 2008 Tom Lane wrote:
>> 5. Figure out why a simple power failure was able to do this to you,
>> and fix it.  The most likely bet is that your disk drives are lying
>> about write completion ... see the PG archives for discussion.
> It could be a caching RAID controller without battery backup unit. 
> Nothing help you in a power failure then, except a good backup.
> Had this with a customer - no more filesystem after reboot...

I hardly understand why such things still happen today. It's one of the 
most important admin tasks to make sure fsync / fua behave as they should.

Wouldn't it be a good idea to add a chapter to the installation docs?

They cover SHM settings and vm.overcommit -- why not a short 
introduction to fsync, write caches, write barriers and a few examples 
of sane and problematic setups as well as links to tools to verify a setup?

Best regards,
Hannes Dorbath

In response to


pgsql-admin by date

Next:From: Lucas SanabioDate: 2008-02-21 22:26:19
Subject: Table was deleted but it still been treated as not
Previous:From: Carol WalterDate: 2008-02-21 21:45:28
Subject: Fwd: Stable Release?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group