Skip site navigation (1) Skip section navigation (2)

Re: Database corrupted

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Yann ROBIN <me(dot)show(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Database corrupted
Date: 2011-12-05 20:31:19
Message-ID: CAOR=d=04pU3x3mWk7dKw70Ctz5o_oBepTqEjWERwqvZJDsE8rA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Mon, Dec 5, 2011 at 1:18 PM, Yann ROBIN <me(dot)show(at)gmail(dot)com> wrote:
>>
>> First things first: Before you do anything else, shut down
>> PostgreSQL and make a copy of the data directory tree.
>>
>> http://wiki.postgresql.org/wiki/Corruption
>>
>
> Did it.
>
>> Second, please post information about your environment.  What
>> version of PostgreSQL is this?  What is your OS?  What hardware is
>> it running on?
>>
>
> Version 9.0.4 on debian squeeze 6.0 running in KVM with virtio (kernel 2.6.32)
> I think we have a hard drive issue.
>
>> Now, please copy from the log at the time of the crash and post all
>> messages, plus any possibly relevant messages in the clients and the
>> OS logs.  Is there a core file from the crash?  Can you get a
>> backtrace from it?
>>
>
> I rm the log file has it was taking too much space because of the 1000
> warning per seconds.
> I feel dumb right now. Sorry.
>
>>
>> It's best to keep notes of exactly what was done.  What was the
>> process description of what you killed?  Which signal did you use?
>> Keep notes as you go.
>>
>
> kill -9 of the writer process

Are you sure you killed all the postgres backends before restarting
the server?  If other backends are still running, with a dead
postmaster, and you restart the server, instant corruption.

In response to

Responses

pgsql-admin by date

Next:From: Kevin GrittnerDate: 2011-12-05 20:46:00
Subject: Re: Database corrupted
Previous:From: Martin SDate: 2011-12-05 20:22:04
Subject: Recover from failover

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group