From: Mark Johnson <mark@remingtondatabasesolutions.com>
To: Raman kumar <raman36127@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: read only error..hard reboot not work as well
Date: Wed, 13 Jul 2011 19:09:18 +0000
Message-ID: <W838101176138351310584158@webmail23> (raw)
It seems postgres is suffering from a file system condition, so your solution 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 machines and run in to a low I/O bandwidth condition, the vm software can put the file systems into a read-only state to prevent data 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. 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 filesystem".
-Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mark@remingtondatabasesolutions.com, raman36127@gmail.com
Subject: Re: read only error..hard reboot not work as well
In-Reply-To: <W838101176138351310584158@webmail23>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox