From: | Strahinja Kustudić <strahinjak(at)nordeus(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Index corruption after proper shut down |
Date: | 2013-11-22 20:39:57 |
Message-ID: | CADKbJJWrZHw_GvB82_2mZ7RQX_B+sok-R02_oMGTpOESXbZHgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry for a reply to myself, but does anyone have any idea what could be
the problem? We would like to try do some testing from your suggestions to
see what could cause this problem and how to mitigate it.
Regards,
Strahinja
On Fri, Nov 15, 2013 at 11:44 AM, Strahinja Kustudić <strahinjak(at)nordeus(dot)com
> wrote:
> Hi all,
>
> Last week we migrated 200+ of our servers from one rack to another and the
> procedure was dead simple: power off server from the OS, unplug it, move it
> to a different rack, plug it in and start it. The problem was that after
> the boot some of the servers had corrupted indexes.
>
> Servers are Dell PowerEdge R420 with H700 RAID controller with BBU, Centos
> 5.9 x64 with Postgres 9.1.9 running on two Intel 330 120GB SSDSC2CT120 (one
> for data, and one for indexes) on XFS (noatime,nobarrier,noquota). Relevant
> Postgres configuration is:
>
> wal_level = minimal
> fsync = on
> wal_sync_method = fdatasync
> full_page_writes = on
> synchronous_commit = off
> wal_buffers = -1
>
> Also we disabled disk write cache on all drives with the MegaCli64
> utility, since the RAID controller should be the one caching since it has a
> BBU.
>
> Does anyone have any idea, why could we get index corruption?
>
> Thanks in advance
>
> Regards,
> Strahinja
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Burgholzer | 2013-11-22 21:29:18 | Re: INSERT performance tuning experiences |
Previous Message | Strahinja Kustudić | 2013-11-22 20:34:30 | Re: Partial Index Creation |