From: | Grzegorz Jaśkiewicz <gryzman(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 13:44:26 |
Message-ID: | 2f4958ff0911260544g68320c6bl5413d72d3df53fb1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Jas | 2009-11-26 13:54:03 | Re: READ ONLY & I/O ERROR |
Previous Message | Sam Jas | 2009-11-26 13:40:45 | READ ONLY & I/O ERROR |