From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Sam Jas <samjas33(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: READ ONLY & I/O ERROR |
Date: | 2009-11-26 16:57:45 |
Message-ID: | dcc563d10911260857g13a101e9nad94194a6f2ed009@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Nov 26, 2009 at 6:40 AM, Sam Jas <samjas33(at)yahoo(dot)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 database it 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 blocks from 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Todd | 2009-11-26 19:02:27 | Re: How use input parameter as path to COPY in function? |
Previous Message | Scott Marlowe | 2009-11-26 16:50:50 | Re: Invalid redo in checkpoint record |