pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: ogjunk-pgjedan@yahoo.com
To: pgsql-admin@postgresql.org
Subject: cannot open segment 1 of relation .... No such file or directory
Date: Mon, 15 Nov 2004 08:25:05 -0800 (PST)
Message-ID: <20041115162505.9994.qmail@web12705.mail.yahoo.com> (raw)

Hello,

I'm using PG 7.3.4 under RedHat 9.0 and I've started noticing the
following type of errors:

  cannot open segment 1 of relation url (target block 537329664): No
such file or directory

How can I determine what exactly is corrupt or missing and which row is
triggering this?

I have found pgfsck (http://svana.org/kleptog/pgsql/pgfsck.html), but
that gives me some funky, unrelated(?) output, like this:


-- Detected database format 7.3
-- Scanning table url
-- Indexing toast table
-- Index complete: 0 toasted tuples
-- Table url(17129): *** SERIOUS ***: No definition found for column 1
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 2
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 3
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 4
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 5
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 6
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 7
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 8
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 9
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 10
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 11
-- Table url(17129): Found old version, continuing
-- Table url(17129): *** SERIOUS ***: No definition found for column 12
-- Table url(17129): Found old version, continuing
-- Table url(17129):Page 0:Tuple 0: Unknown type timestamp (1114)
-- Table url(17129):Page 0:Tuple 0: Unknown type timestamp (1114)
-- Table url(17129):Page 0:Tuple 1: Unknown type timestamp (1114)
-- Table url(17129):Page 0:Tuple 1: Unknown type timestamp (1114)
...
... keeps going through Pages with the same timestamp error ...
...

As far as I can tell, the above errors/warnings are not related to the
error I am getting.


I do have a dump of this DB, in case that can be used to fix the
corrupt tuple.

I dump this DB every night with:

  pg_dump -d xxx --clean --inserts --column-inserts --format=P -v


Any help would be much appreciated.

Thanks,
Otis




view thread (3+ messages)  latest in thread

Message-ID: <20041115162505.9994.qmail@web12705.mail.yahoo.com>
Permalink:  ../20041115162505.9994.qmail@web12705.mail.yahoo.com/
Also on:    postgresql.org/message-id/20041115162505.9994.qmail@web12705.mail.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: ogjunk-pgjedan@yahoo.com
  Subject: Re: cannot open segment 1 of relation .... No such file or directory
  In-Reply-To: <20041115162505.9994.qmail@web12705.mail.yahoo.com>
  References: <20041115162505.9994.qmail@web12705.mail.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox