Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id ED978B5DC45 for ; Wed, 13 Jul 2011 16:09:30 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 36757-05-4 for ; Wed, 13 Jul 2011 19:09:25 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from omr9.networksolutionsemail.com (omr9.networksolutionsemail.com [205.178.146.59]) by mail.postgresql.org (Postfix) with ESMTP id 1BFD8B5DCC4 for ; Wed, 13 Jul 2011 16:09:23 -0300 (ADT) Received: from cm-omr2 (mail.networksolutionsemail.com [205.178.146.50]) by omr9.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p6DJ9IcJ018623 for ; Wed, 13 Jul 2011 15:09:22 -0400 X-Authenticated-IP: 205.178.146.50 Received: from [205.178.146.50] ([205.178.146.50:48464] helo=webmail23) by cm-omr2 (envelope-from ) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id A9/83-04012-E5DED1E4; Wed, 13 Jul 2011 15:09:18 -0400 Received: from 65.222.202.202 (mark@remingtondatabasesolutions.com [65.222.202.202]) by webmail23 (Netsol 11.2.30) with WEBMAIL id 3835; Wed, 13 Jul 2011 19:09:18 +0000 From: "Mark Johnson" To: "Raman kumar" , pgsql-admin@postgresql.org Importance: Normal Sensitivity: Normal Message-ID: X-Mailer: Network Solutions Webmail, Build 11.2.30 X-Originating-IP: [65.222.202.202] X-Forwarded-For: [(null)] Date: Wed, 13 Jul 2011 19:09:18 +0000 Subject: Re: read only error..hard reboot not work as well MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="--=_vm_0011_W8381011761_3835_1310584158" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.735 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_NUMERIC_HELO=1.164 X-Spam-Level: X-Archive-Number: 201107/92 X-Sequence-Number: 37871 ----=_vm_0011_W8381011761_3835_1310584158 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable It seems postgres is suffering from a file system condition, so your solu= tion lies there and not with postgres. There are many reasons why a file = system can become read-only. For example, if you are using virtual machin= es and run in to a low I/O bandwidth condition, the vm software can put t= he file systems into a read-only state to prevent data corruption. Some c= lusterware and storage hardware vendors also do this on purpose to preven= t corruption. Without knowing more about your system there are too many p= ossbiel causes to list them here. My suggestion is to search the Internet= for a possible cause/solution. If, for example, you are using vmware on = Linux then you might want to Google for "vmware linux read only filesyste= m". -Mark ----=_vm_0011_W8381011761_3835_1310584158 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

 

It seems postgres is suffering from a file system condition, so your&n= bsp;solution lies there and not with postgres.  There are many reaso= ns why a file system can become read-only.  For example, if you are = using virtual machines and run in to a low I/O bandwidth condition, the v= m software can put the file systems into a read-only state to prevent dat= a corruption.  Some clusterware and storage hardware vendors also do= this on purpose to prevent corruption.  Without knowing more about = your system there are too many possbiel causes to list them here.  M= y suggestion is to search the Internet for a possible cause/solution= .  If, for example, you are using vmware on Linux then you might wan= t to Google for "vmware linux read only filesystem".

-Mark

----=_vm_0011_W8381011761_3835_1310584158--