From: Mik Rose <mrose@power-soft.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-sql@postgresql.org <pgsql-sql@postgresql.org>
Subject: Re: (pgsql8.4) DATA Corruption
Date: Fri, 19 Aug 2011 13:27:57 -0700
Message-ID: <0F87A7E6-6BF1-43BF-9299-BD94E28547FB@power-soft.com> (raw)
In-Reply-To: <CAOR=d=05dcTFyV2zv1hPjUu4iTXT1w+sTySErF-PrmmB9jT=9g@mail.gmail.com>
References: <F9528C0916A72145B548F5A758993ACC0EEFB41A@powerexchange.power-soft.net>
<CAOR=d=05dcTFyV2zv1hPjUu4iTXT1w+sTySErF-PrmmB9jT=9g@mail.gmail.com>
Thanks for the suggestions Scott.
I was looking at the zero_damage_page option and enabled it in my postgres.conf. I saw that it detected bad pages and zero'd them out during a number of reindex and a vacuum's.
Now when i reindex though, I am getting this error.
NOTICE: table "pg_foreign_server" was reindexedERROR: could not create unique index "pg_toast_57366_index"
DETAIL: Table contains duplicated values.
ERROR: could not create unique index "pg_toast_57366_index"
DETAIL: Table contains duplicated values.
On 2011-08-19, at 1:02 PM, Scott Marlowe wrote:
> On Fri, Aug 19, 2011 at 1:08 PM, Mikola Rose <mrose@power-soft.com> wrote:
>> Happy Friday people!
>>
>>
>>
>> I was wondering if anyone had any suggestions on how to resolve this
>> issue... I am moving otrs to another server and during the backup process I
>> am running into this error
>>
>> pg_dump: dumping contents of table article_attachment
>>
>>
>>
>>
>>
>> pg_dump: SQL command failed
>>
>> pg_dump: Error message from server: ERROR: unexpected chunk number 7
>> (expected 6) for toast value 77281 in pg_toast_57366
>>
>>
>>
>>
>>
>> pg_dump: The command was: COPY public.article_attachment (id, article_id,
>> filename, content_size, content_type, content, create_time, create_by,
>> change_time, change_by, content_id, content_alternative) TO stdout;
>>
>>
>>
>>
>>
>> pg_dump: *** aborted because of error
>>
>>
>>
>>
>>
>> I have tried a vacuum and reindex with no successes.
>
> You'll likely have to figure which blocks are corrupted, and copy out
> the good data using a where clause the excludes it, then get what you
> can out of it, truncate the table, and reinsert the data.
>
> Then figure out what part of your hardware is / might be dodgy. mem
> test, disk check, etc.
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-sql@postgresql.org
Cc: mrose@power-soft.com, scott.marlowe@gmail.com
Subject: Re: (pgsql8.4) DATA Corruption
In-Reply-To: <0F87A7E6-6BF1-43BF-9299-BD94E28547FB@power-soft.com>
* 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