Re: READ ONLY & I/O ERROR

How can i enable journaling as i am not so good at OS & H/W level. Can you give me some detail description.

Thanks
Sam Jas

--- On Thu, 26/11/09, Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> wrote:

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
Subject: Re: [GENERAL] READ ONLY & I/O ERROR
To: "Sam Jas" <samjas33(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Date: Thursday, 26 November, 2009, 1:44 PM

On Thu, Nov 26, 2009 at 1:40 PM, 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

32 GB RAM
assemble hardware
 
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. this looks more like filesystem corruption.
What's the FS database is running on ? presumably ext3 (cos it is centos5).

If possible, consider checking the root cause of FS corruption, possibly test on other FS (xfs?).
Maybe you should also try to enable journaling, if you run in ext2/3 mode.
 

--
GJ

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