Index corruption after proper shut down - Mailing list pgsql-admin

From Strahinja Kustudić
Subject Index corruption after proper shut down
Date
Msg-id CADKbJJWBF4cg5h2Ww+okz6QPU1egvvgp+QU70v-ZEHM+2+KCQw@mail.gmail.com
Whole thread Raw
Responses Re: Index corruption after proper shut down  (Strahinja Kustudić <strahinjak@nordeus.com>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Karl Hafner
Date:
Subject: Re:
Next
From: Thara Vadakkeveedu
Date:
Subject: Re: checking if sequence exists