Re: READ ONLY & I/O ERROR - Mailing list pgsql-general

From Scott Marlowe
Subject Re: READ ONLY & I/O ERROR
Date
Msg-id dcc563d10911260857g13a101e9nad94194a6f2ed009@mail.gmail.com
Whole thread Raw
In response to READ ONLY & I/O ERROR  (Sam Jas <samjas33@yahoo.com>)
Responses Re: READ ONLY & I/O ERROR  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-general
On Thu, Nov 26, 2009 at 6:40 AM, Sam Jas <samjas33@yahoo.com> wrote:
>
> Hi Folks,
>
> I am frequently getting read-only file system error on my server.
>
> We are using postgreSQL, GridSQL database. The size of database is very huge.
> Architecture Details:
> CentOS 5.3 64 bit Areca high point rocket raid 3520 8 port

Areca doesn't make the high point rocket raid cards (which are medium
quality RAID cards).

> 32 GB RAM
> assemble hardware

Did you follow proper ESD precautions when building this machine??

> We are daily processing millions of rows and loadiing into database. We have marked that when we create a new
databaseit worked fine upto 20 or 25 days. After that we 
> are getting errors like "read only file system" , data is corrupted. Therefore we are running fsck to remove bad
blocksfrom the disk. However, after running fsck also we are getting the same error. 
>
> I will appreciate you if somebody help me to get rid out of this issue.

Sounds like your hardware is bad.  Could be mobo / cpu / memory or
RAID card.  Does this machine "hang" every so often or anything?

I'd run memtest86+ on it first to confirm good cpu / memory / mobo.

Quick factoid from my days as an electronics instructor in the USAF,
95% of all ESD induced failures are latent in nature, either resulting
in catastrophic failure or thermal degradation some months or years
down the road.

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Invalid redo in checkpoint record
Next
From: Bill Todd
Date:
Subject: Re: How use input parameter as path to COPY in function?