From: Hannes Dorbath <light@theendofthetunnel.de>
To: Michael Monnerie <michael.monnerie@it-management.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Power outage borked things (8.1.10)...
Date: Thu, 21 Feb 2008 23:00:08 +0100
Message-ID: <47BDF468.3090001@theendofthetunnel.de> (raw)
In-Reply-To: <200802202205.58380@zmi.at>
References: <47BBF298.4010108@fastmail.net>
<8625.1203523828@sss.pgh.pa.us>
<200802202205.58380@zmi.at>
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
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: light@theendofthetunnel.de, michael.monnerie@it-management.at, tgl@sss.pgh.pa.us
Subject: Re: Power outage borked things (8.1.10)...
In-Reply-To: <47BDF468.3090001@theendofthetunnel.de>
* 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