Re: READ ONLY & I/O ERROR

We are getting the below errors after 20 or 25 days of database creation.

ERROR: could not
open relation 1919829/1152694/1921473: Read-only file system
ERROR: could not read block 312320 of relation 1964206/1152694/1981329:
Input/output error

If we create a new database the problem is
repeated after 20 or 25 days. Until then we don't have any issues with the new
database.

The size of database is very huge. We are loading millions of
records every day and also fetching from the database is also high. Even the
disks are not full. We are not dropping the old database.

What is the
reason for this issue?

How can we ensure that it is not a database
issue?

We are using
GridSQL: 1.1.0.9
PostgreSQL 8.3

Architecture Details:
CentOS 5.3 64 bit Areca high point rocket raid
3520 8 port
32 GB RAM

--
Thanks
Sam Jas

--- On Mon, 30/11/09, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:

From: Greg Smith <greg(at)2ndquadrant(dot)com>
Subject: Re: [GENERAL] READ ONLY & I/O ERROR
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "Sam Jas" <samjas33(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Date: Monday, 30 November, 2009, 8:29 PM

Scott Marlowe wrote:
> Areca doesn't make the high point rocket raid cards (which are medium
> quality RAID cards).
>   
On a good day maybe.  HighPoint is a pretty miserable RAID vendor--in the same league as Promise from what I've seen as far as their Linux driver support goes.  In generally, and for reasons I'm not completely sure of, everyone selling "fake RAID" cards seems to be completely incompetent.  The page at http://linuxmafia.com/faq/Hardware/sata.html hasn't been updated in a while, but as of 2007 all the current HighPoint cards were still based on closed-source drivers only.  Completely worthless hardware IMHO.

> Sounds like your hardware is bad.  Could be mobo / cpu / memory or
> RAID card.  Does this machine "hang" every so often or anything?
>   
It's not out of the question for this sort of problem to be caused by a bad driver too.  In this case it seems more likely it's a drive failure though.

-- Greg Smith    2ndQuadrant   Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com  www.2ndQuadrant.com

-- Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/