pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Juliann Meyer <Julie.Meyer@noaa.gov>
To: pgsql-admin@postgresql.org
Subject: vacuumdb problem v7.4.8
Date: Tue, 10 Jul 2007 09:03:25 -0500
Message-ID: <469391AD.3030206@noaa.gov> (raw)

Have 14 systems scattered across the country where... hardware is 
identical, all run linux OS RHE4.0 with postgresql v7.4.8.
The hardware is about 4 years old and is scheduled for replacement 
sometime next year.
The database structure is identical on each system, the difference is in 
the data that is stored within each database, as it varies from site to 
site and the amount of data varies as well, so no two databases are 
exactly the same size or contains the same data.
Every system runs a "vacuum analyze" 2 to 3 times per day on this 
database and a nightly cron job does a pg_dump of the database.

One site is getting errors with the "vacuum analyze" so it basically 
fails and similar error then occurs when the nightly backups is run.
The error in the vacuum's logfile looks like this:
   INFO:  vacuuming "public.pecrsep"

   vacuumdb: vacuuming of database "adb_ob72orn" failed: ERROR:  could not
   read block 18658 of relation "pecrsep_time_ind": Input/output error

The Elec. Technicians at first thought it was an issue with one of the 
hard drives, but a very thorough check of the hardware has eliminated 
this possibility.
So far they have tried re-installing everything as if its the first time 
from scratch on the existing hardware with no success.  As a last 
resort, the hardware was replaced with a spare (similar age) and 
everything installed from scratch.  The database and related apps ran 
fine for about a week and then the same type of error occurred again 
with vacuumdb and pg_dump and it appears to be occurring with the same 
database table.

At this point, we don't know what else to try, and the problem hasn't 
occurred anywhere else  (fortunately).  Does anyone have any idea what 
this error means and how to fix it. 

Any suggestions, ideas, etc would be greatly appreciated.
Julie Meyer

Attachments:

julie.meyer.vcf (text/x-vcard, 247B) download begin:vcard fn:A. Juliann Meyer org:National Weather Service;Missouri Basin River Forecast Center adr;dom:;;;Pleasant Hill;MO;64080 email;internet:julie.meyer@noaa.gov title:Sr. Hydrologist - Data Systems x-mozilla-html:FALSE version:2.1 end:vcard

view thread (2+ messages)  latest in thread

Message-ID: <469391AD.3030206@noaa.gov>
Permalink:  ../469391AD.3030206@noaa.gov/
Also on:    postgresql.org/message-id/469391AD.3030206@noaa.gov

 · 

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: Julie.Meyer@noaa.gov
  Subject: Re: vacuumdb problem v7.4.8
  In-Reply-To: <469391AD.3030206@noaa.gov>

* 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