On Thu, Nov 26, 2009 at 6:40 AM, Sam Jas <samja...@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 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. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
