From: | Oleg Serov <serovov(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgresql + corrupted disk = data loss. (Need help for database recover) |
Date: | 2011-12-02 01:10:15 |
Message-ID: | CAMkKa8D3gR0AxOM5LGYYGZ-X9CMdcnJ7JfLzK3w8iRmkU9RKPA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
And, i'm an idiot.
My DB version:
PostgreSQL 8.4.9 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC)
4.1.2 20080704 (Red Hat 4.1.2-51), 64-bit
2011/12/2 Oleg Serov <serovov(at)gmail(dot)com>
> Hello, i have a problem.
>
> I've got a production server, working fine. Then i've got strange error:
> > ERROR: right sibling's left-link doesn't match: block 147 links to 407
> instead of expected 146 in index "order_status_key"'
> And decidet to backup all server. So i shut-down VPS with server and
> backup all data.
> Then, after i booted it - and then - i've got Data loss.
>
> I've lost data, that have been written to DB around 10-100 hours
> (different tables, have different last updated value).
>
> Then i've analyzed log, and found this:
> 7 days ago appears this errors:
> db= LOG: could not rename temporary statistics file
> "pg_stat_tmp/pgstat.tmp" to "pg_stat_tmp/pgstat.stat":
> db= WARNING: pgstat wait timeout
> ERROR: missing chunk number 0 for toast value 2550017 in pg_toast_17076
>
> 5 days ago:
> a lot of: ERROR: xlog flush request F/DC1A22D8 is not satisfied ---
> flushed only to F/526512E0
> 83238 db= WARNING: could not write block 54 of base/16384/2619
> 83239 db= CONTEXT: writing block 54 of relation base/16384/2619
>
> And today:
> 18 db= LOG: could not open file "pg_xlog/000000010000000F00000052"
> (log file 15, segment 82):
> 19 db= ERROR: xlog flush request F/DC1A22D8 is not satisfied ---
> flushed only to F/52FDF0E0
>
> There is any ability to recover fresh data from database?
>
> Thanks!
>
>
>
--
С уважением
Олег
From | Date | Subject | |
---|---|---|---|
Next Message | Lonni J Friedman | 2011-12-02 01:36:00 | Re: returning rows from an implicit JOIN where results either exist in both tables OR only one table |
Previous Message | Oleg Serov | 2011-12-02 01:08:10 | Postgresql + corrupted disk = data loss. (Need help for database recover) |