From: Tony Capobianco <tcapobianco@prospectiv.com>
To: pgsql-admin@postgresql.org
Subject: Re: drive failure
Date: Thu, 31 Mar 2011 09:41:27 -0400
Message-ID: <1301578887.2019.4.camel@tony1.localdomain> (raw)
In-Reply-To: <1301575122.2019.2.camel@tony1.localdomain>
References: <1301575122.2019.2.camel@tony1.localdomain>
We were able to determine through a few of our queries that an index was
corrupt. We did this through the process of elimination however. As a
result, I have two questions:
How can I determine that we have a corrupt index?
How can I determine which datafile (5875980.x) is related to which
tablespace?
On Thu, 2011-03-31 at 08:38 -0400, Tony Capobianco wrote:
> Hello,
> He had a drive fail in an array and the spare kicked in to replace the
> failed drive. However, when I query a specific table, I get the below
> error:
>
> ERROR: could not open file
> "pg_tblspc/16412/PG_9.0_201008051/16419/5875980.7" (target block
> 2968776487): No such file or directory
>
>
> When I change to this directory, the file in question does not exist.
> Am I to assume that I'm completely hosed? If the spare kicked in, what
> happened to the file listed above? Any hints would be most appreciated.
>
> Thanks.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tcapobianco@prospectiv.com
Subject: Re: drive failure
In-Reply-To: <1301578887.2019.4.camel@tony1.localdomain>
* 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