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: | 47BDF468.3090001@theendofthetunnel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Lucas Sanabio | 2008-02-21 22:26:19 | Table was deleted but it still been treated as not |
Previous Message | Carol Walter | 2008-02-21 21:45:28 | Fwd: Stable Release? |