From: | Ken Caruso <ken(at)ipl31(dot)net> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | 9.0.4 Data corruption issue |
Date: | 2011-07-16 11:05:15 |
Message-ID: | CAMg8r_rzsTn+pR0+A0xCXS73o5QsTdgsisW9AHG6jEm87r1FCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
Had a DB that had bloated due to lots of updates and insuffcient auto vacuum
settings. Attempted the following in the following order:
VACUUM VERBOSE full tablename;
CLUSTER tablename;
Did the full first to ensure that the cluster had enough space to run.
The db had already been previously clustered to an index. At some point
during the VACUUM I started seeing the following errors in the logs:
CONTEXT: writing block 12125253 of relation base/2651908/652397108
WARNING: could not write block 12125253 of base/2651908/652397108
DETAIL: Multiple failures --- write error might be permanent.
Also seeing the same error for block 12125253, 2978.
And the cluster failed as well. I have attempted a check point using
pg_start_backup() and that failed as well.
The system is still running and I have yet to shut it down. I am hoping to
find out what possibilities I have if any to recover from this. Also how do
I avoid this in the future?
-Ken
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Caruso | 2011-07-16 11:43:12 | Re: 9.0.4 Data corruption issue |
Previous Message | Isabella Ghiurea | 2011-07-15 19:40:00 | PG 8.4 and identity columns |