DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=Sm9m+hlu1VGHHyC1J/e4KckgmYDBMhtqgYKiDZllEJkCYvucqWGkVpQaMMhLYSM5tk
	BYT/s8ut+Lxbd01zQrK7CiYiu/H5u/mdhg+24z/N1+YQ6LgihYnnKMuDPMYgXIuiaNsw
	LxGwxAxnHOIGDTRA1O091z34mLOn8TYc1wrQQ=
MIME-Version: 1.0
In-Reply-To: <9762.1267234886@sss.pgh.pa.us>
References: <e09f34d01002261212s4e1ea86csca52f95a274fdfe2@mail.gmail.com>
	<9762.1267234886@sss.pgh.pa.us>
Date: Sat, 27 Feb 2010 01:41:08 -0600
Message-ID: <e09f34d01002262341s38ff849cp8cce6a58d24620d@mail.gmail.com>
Subject: Re: db recovery after hd crash (could not open relation
	1663/16385/16400: No such file or directory)
From: Roland Wells <roland.wells@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 26, 2010 at 7:41 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Roland Wells <roland.wells@gmail.com> writes:
>> On new hardware, installed pg8.1 and restored data directory and
>> attempted to start pg. After fixing some config differences, it
>> complained of a missing pg_clog/xxx file. After searching the archives
>> for hints, added a file of zero's and pg starts successfully. The db
>> in question exists with what appears to be intact structure. When
>> attempting to dump the db ran into the error: "could not open relation
>> 1663/16385/16400: No such file or directory" and run into similar
>> errors (with different relation numbers) trying to select * from
>> certain tables.
>
>> I'm stuck here. Assuming the damage to filesystem, what is the best a
>> way forward? Does the relation error indicate damage to the data? or
>> to an index??? Is there a process I can do to try and salvage partial
>> data?
>
> You can look for the third number in pg_class.relfilenode to see exactly
> which table or index it's complaining about. =A0If it's happening in
> pg_dump then it's probably a table not an index, unfortunately.
> Not sure there's much you can do except go back to your last backup
> --- PG can't do anything to recover data that the filesystem has lost
> track of, which is what this is sounding like.
>
> But having said that, did you try fsck'ing the DD image to see if fsck
> could recover any files?
>
Thanks for the replies:

A look at pg_class.relfilenode seems to confirm that tables are
missing (7 out of 52 tables in the db are missing). I did do an fsck
on the restored disk image and there is quite a few files in the
lost+found. I am still wading through them at the moment, but not
hopeful of recovery this way as many I've looked at so far appear to
only be partial files. Additionally, several of the tables in the db
show far less rows than should exist, so there may be damage to those
files as well...

Probably will head to the backup. Thanks again. Roland