pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alejandro Brust <alejandrob@pasteleros.org.ar>
To: pgsql-admin@postgresql.org
Subject: Re: ERROR: could not open file "base/125542/12631" Corruption?
Date: Fri, 04 Oct 2013 13:53:20 -0300
Message-ID: <524EF280.5040502@pasteleros.org.ar> (raw)
In-Reply-To: <CAB9893jR-_zaRxeRc0b4rapWLa-M-=Z-vSKt-vxD5uOhFs-z9w@mail.gmail.com>
References: <CAB9893jR-_zaRxeRc0b4rapWLa-M-=Z-vSKt-vxD5uOhFs-z9w@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>


El 04/10/2013 11:40, Mike Broers escribió:
> Hello, our postgresql 9.2.4 qa database (thankfully its just qa) seems
> to be hosed.  
>
> Starting at around 3:39am last night I started seeing errors about
> missing files and now I cannot run a pgdump or a vacuum without it
> complaining about files that it cannot find with errors like this:
> ERROR: could not open file "base/125542/12631". When I check the
> filesystem the files are indeed not there.  The 1am regular vacuum
> completed and its log is clean.  The postgres log is clean before
> these errors occurred.
>
> Since this is qa we do not perform backups, and the solution if we
> cannot repair the problem will be to create a fresh qa server but I am
> intrigued about how to determine the source of the problem and the
> extent of the problem.  
>
> Is there a way to force vacuum to continue on errors or an alternate
> way to help determine all the missing files?  
>
> It might be totally unrelated, but yesterday morning on this qa server
> I stopped postgres, and created a symlink to pg_xlog so that it was
> writing to a different volume, and restarted.  This was working fine
> all day so its possibly a red herring but I thought I should mention it.
>
> Any advice is appreciated, thanks!  
>
>
/Hello

U could try  some like "SET/ zero_damaged_pages = on"    and perform a
vacuum-db and may be pg_dump
hope it help!

view thread (6+ messages)  latest in thread

Message-ID: <524EF280.5040502@pasteleros.org.ar>
Permalink:  ../524EF280.5040502@pasteleros.org.ar/
Also on:    postgresql.org/message-id/524EF280.5040502@pasteleros.org.ar

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: alejandrob@pasteleros.org.ar
  Subject: Re: ERROR: could not open file "base/125542/12631" Corruption?
  In-Reply-To: <524EF280.5040502@pasteleros.org.ar>

* 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