From: Craig Ringer <ringerc@ringerc.id.au>
To: Terry Schmitt <tschmitt@schmittworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Data corruption after SAN snapshot
Date: Wed, 08 Aug 2012 09:11:02 +0800
Message-ID: <5021BCA6.7030000@ringerc.id.au> (raw)
In-Reply-To: <CAOOcyswLYBfJDuvNBPMkiNCGNKgK=SiexUuTVHCh2O+Y1T-sLw@mail.gmail.com>
References: <CAOOcyswLYBfJDuvNBPMkiNCGNKgK=SiexUuTVHCh2O+Y1T-sLw@mail.gmail.com>
On 08/08/2012 06:23 AM, Terry Schmitt wrote:
> Anyone have a solid method to test if fdatasync is working correctly or
> thoughts on troubleshooting this?
Try diskchecker.pl
https://gist.github.com/3177656
The other obvious step is that you've changed three things, so start
isolation testing.
- Test Postgres Plus Advanced Server 8.4, which you knew worked, on your
new file system and OS.
- Test PP9.1 on your new OS but with ext3, which you knew worked
- Test PP9.1 on your new OS but with ext4, which should work if ext3 did
- Test PP9.1 on a copy of your *old* OS with the old file system setup.
- Test mainline PostgreSQL 9.1 on your new setup to see if it's PP specific.
Since each test sounds moderately time consuming, you'll probably need
to find a way to automate. I'd first see if I could reproduce the
problem when running PgBench against the same setup that's currently
failing, and if that reproduces the fault you can use PgBench with the
other tests.
--
Craig Ringer
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: ringerc@ringerc.id.au, tschmitt@schmittworks.com
Subject: Re: Data corruption after SAN snapshot
In-Reply-To: <5021BCA6.7030000@ringerc.id.au>
* 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