From: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Bad crash, pg_clog files missing ... ? |
Date: | 2003-03-07 04:46:20 |
Message-ID: | 20030307004031.O5683@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
'K, that's what I ended up doing ... the server crashed *really* hard, but
I had a backup from 24hrs previous that I used to do restores ... I kinda
figured that I was lost :(
But, the files available are/where ...
venus# ls -lt
total 1168
-rw------- 1 pgsql pgsql 81920 Mar 6 19:50 0168
-rw------- 1 pgsql pgsql 262144 Mar 5 20:06 0167
-rw------- 1 pgsql pgsql 262144 Mar 5 14:10 0166
-rw------- 1 pgsql pgsql 262144 Mar 5 09:03 0165
-rw------- 1 pgsql pgsql 262144 Mar 5 02:08 0164
On Thu, 6 Mar 2003, Tom Lane wrote:
> "Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> > FATAL 2: open of /usr/local/pgsql/5432/pg_clog/06F6 failed: No such file or directory
>
> > The RAID controller went on our server today ... is it safe to just
> > 'touch' the files, or is this a 'restore from backup and deal with the
> > losses' sort of thing? :(
>
> What range of filenames is actually in $PGDATA/pg_clog/ ?
>
> I suspect 06F6 is well beyond that range, in which case this error
> implies corrupted table files, in which case "restore from backup"
> is the indicated course of action :-(
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-03-07 05:00:42 | Re: pgsql.com website store |
Previous Message | Tom Lane | 2003-03-07 04:44:15 | Re: Partial index on date column |