<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Why my Linux server ext3 filesystem go read-only?</title> <atom:link href="http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html/feed" rel="self" type="application/rss+xml" /><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html</link> <description>This is a Linux sys admin journal by Vivek about sys admin work, Linux tips &#38; tricks, hacks, news and more.</description> <lastBuildDate>Fri, 10 Feb 2012 20:37:43 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: ARAO</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-176554</link> <dc:creator>ARAO</dc:creator> <pubDate>Tue, 06 Dec 2011 11:08:41 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-176554</guid> <description>Really Really it was of great use (mount -o remount /) ..Thanks :-)</description> <content:encoded><![CDATA[<p>Really Really it was of great use (mount -o remount /) ..Thanks :-)</p> ]]></content:encoded> </item> <item><title>By: Arun</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-175285</link> <dc:creator>Arun</dc:creator> <pubDate>Fri, 28 Oct 2011 10:22:41 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-175285</guid> <description>Try below am succees
echo j &gt; /proc/sysrq-trigger
-j Forcibly &quot;Just thaw it&quot; - filesystems frozen by the FIFREEZE ioctl</description> <content:encoded><![CDATA[<p>Try below am succees<br
/> echo j &gt; /proc/sysrq-trigger</p><p>-j Forcibly &#8220;Just thaw it&#8221; &#8211; filesystems frozen by the FIFREEZE ioctl</p> ]]></content:encoded> </item> <item><title>By: KP</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-174877</link> <dc:creator>KP</dc:creator> <pubDate>Sat, 15 Oct 2011 22:57:30 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-174877</guid> <description>Thank you for this article, I&#039;ve encountered the same problem. My server was not accessible anymore, nothing to find in the logs after reboot.
Now I was connected with ssh to update the system and it suddenly was read-only. I guess my usb drive is defect somehow.</description> <content:encoded><![CDATA[<p>Thank you for this article, I&#8217;ve encountered the same problem. My server was not accessible anymore, nothing to find in the logs after reboot.<br
/> Now I was connected with ssh to update the system and it suddenly was read-only. I guess my usb drive is defect somehow.</p> ]]></content:encoded> </item> <item><title>By: Ringo</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-173972</link> <dc:creator>Ringo</dc:creator> <pubDate>Thu, 15 Sep 2011 03:28:14 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-173972</guid> <description># mount -o remount /
did not work. The following error came up:
-bash: /bin/mount: Input/output error</description> <content:encoded><![CDATA[<p># mount -o remount /<br
/> did not work. The following error came up:</p><p>-bash: /bin/mount: Input/output error</p> ]]></content:encoded> </item> <item><title>By: Enzo</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-173485</link> <dc:creator>Enzo</dc:creator> <pubDate>Mon, 22 Aug 2011 14:55:23 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-173485</guid> <description>mount -o remount /     did not work for me. All I get is this:
[root@starlight ~]# mount -o remount /
mount: block device /dev/VolGroup00/LogVol00 is write-protected, mounting read-only
[root@starlight ~]# touch shit
touch: cannot touch `shit&#039;: Read-only file system
[root@starlight ~]#</description> <content:encoded><![CDATA[<p>mount -o remount /     did not work for me. All I get is this:</p><p>[root@starlight ~]# mount -o remount /<br
/> mount: block device /dev/VolGroup00/LogVol00 is write-protected, mounting read-only<br
/> [root@starlight ~]# touch shit<br
/> touch: cannot touch `shit&#8217;: Read-only file system<br
/> [root@starlight ~]#</p> ]]></content:encoded> </item> <item><title>By: Travis</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-172229</link> <dc:creator>Travis</dc:creator> <pubDate>Sat, 02 Jul 2011 08:37:14 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-172229</guid> <description>Dude....that mount -o remount / saved my butt....
Truly....you are the man.
Where did you learn that? Really....</description> <content:encoded><![CDATA[<p>Dude&#8230;.that mount -o remount / saved my butt&#8230;.</p><p>Truly&#8230;.you are the man.</p><p>Where did you learn that? Really&#8230;.</p> ]]></content:encoded> </item> <item><title>By: Sachin</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-172091</link> <dc:creator>Sachin</dc:creator> <pubDate>Fri, 24 Jun 2011 04:45:55 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-172091</guid> <description>We have virtual server running RHEL 3. There are four disk sda, sdb, sdc and sdd.
Recently twice the server went into hung mode and also console appeared blank.
We had to hard boot the machine both the times.When server was up and running, we found in system logs that 3 disks were fine,  but 4th disk sdd had gone in read-only mode and need recovery to get in write mode. We recorded the logs and presented to client and suggested them to do fsck.
But later on after sometime the recovery got completed and the partition was enabled in rw mode.
Now the strange thing is that it had time-stamp when it shown the message that disk went into read only mode.
So my question is that does the system do recovery in log buffer to reduce IO contention. And when it takes the partition for recovery then does it record the same time and after it is completed then does it push to disk with the same timestamp?</description> <content:encoded><![CDATA[<p>We have virtual server running RHEL 3. There are four disk sda, sdb, sdc and sdd.<br
/> Recently twice the server went into hung mode and also console appeared blank.<br
/> We had to hard boot the machine both the times.When server was up and running, we found in system logs that 3 disks were fine,  but 4th disk sdd had gone in read-only mode and need recovery to get in write mode. We recorded the logs and presented to client and suggested them to do fsck.</p><p>But later on after sometime the recovery got completed and the partition was enabled in rw mode.</p><p>Now the strange thing is that it had time-stamp when it shown the message that disk went into read only mode.<br
/> So my question is that does the system do recovery in log buffer to reduce IO contention. And when it takes the partition for recovery then does it record the same time and after it is completed then does it push to disk with the same timestamp?</p> ]]></content:encoded> </item> <item><title>By: coyote</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-171892</link> <dc:creator>coyote</dc:creator> <pubDate>Mon, 13 Jun 2011 00:13:25 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-171892</guid> <description>hi thanks man, this saved my day...... may the force be with u, Erik dude! \\//,</description> <content:encoded><![CDATA[<p>hi thanks man, this saved my day&#8230;&#8230; may the force be with u, Erik dude! \\//,</p> ]]></content:encoded> </item> <item><title>By: Emil@start a blog</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-171556</link> <dc:creator>Emil@start a blog</dc:creator> <pubDate>Wed, 25 May 2011 22:20:03 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-171556</guid> <description>Thanks for the mount - o remount / ... I will have to try that.  I rebooted a system that had the issue.  I&#039;ll have to remember to try this when it happens again.  Still don&#039;t know the root cause yet.</description> <content:encoded><![CDATA[<p>Thanks for the mount &#8211; o remount / &#8230; I will have to try that.  I rebooted a system that had the issue.  I&#8217;ll have to remember to try this when it happens again.  Still don&#8217;t know the root cause yet.</p> ]]></content:encoded> </item> <item><title>By: Ggunzelman</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-170702</link> <dc:creator>Ggunzelman</dc:creator> <pubDate>Tue, 19 Apr 2011 18:26:24 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-170702</guid> <description>So just on a whim and for no good reason (I figured the system was hosed by now) I rebooted and did another mount -o remount /. I still could not login ssh. I noticed several deamons failing including auditd. I still could not log in to the Asterisk web manager interface. I couldn&#039;t even run Asterisk CLI. So I ran yum update kernel followed by yum update. It found a kernel update and installed it. It found 209 other updates and installed them. Mind you when I set this up last week I did all the updates it could find. So would I be correct in assuming that these updates were the result of data corruption. Because now another reboot produces a good working system.</description> <content:encoded><![CDATA[<p>So just on a whim and for no good reason (I figured the system was hosed by now) I rebooted and did another mount -o remount /. I still could not login ssh. I noticed several deamons failing including auditd. I still could not log in to the Asterisk web manager interface. I couldn&#8217;t even run Asterisk CLI. So I ran yum update kernel followed by yum update. It found a kernel update and installed it. It found 209 other updates and installed them. Mind you when I set this up last week I did all the updates it could find. So would I be correct in assuming that these updates were the result of data corruption. Because now another reboot produces a good working system.</p> ]]></content:encoded> </item> <item><title>By: Ggunzelman</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-170701</link> <dc:creator>Ggunzelman</dc:creator> <pubDate>Tue, 19 Apr 2011 17:17:23 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-170701</guid> <description>I cannot figure this out. I am relatively new to Centos. My AsteriskNow system came with Centos and after a few days it went read only. I fixed it the first time with mount -o remount / only to have it happen again 2 days later. Now that doesn&#039;t work. I have been down for two days. Linux Rescue  ??? How exactly. I tried to do this with LiveCD and it complains about ext4 missing. I am so frustrated I want to give it up but it is the phones and I have a year long SIP contract. Any help would be appreciated.
Centos 2.6.18
AsteriskNow 1.8
Hardware, Intel ITX 1.2GHz Celeron, 1Gb memory, 4Gb SSD drive, TDM800P(4 FXS, 4FXO)</description> <content:encoded><![CDATA[<p>I cannot figure this out. I am relatively new to Centos. My AsteriskNow system came with Centos and after a few days it went read only. I fixed it the first time with mount -o remount / only to have it happen again 2 days later. Now that doesn&#8217;t work. I have been down for two days. Linux Rescue  ??? How exactly. I tried to do this with LiveCD and it complains about ext4 missing. I am so frustrated I want to give it up but it is the phones and I have a year long SIP contract. Any help would be appreciated.<br
/> Centos 2.6.18<br
/> AsteriskNow 1.8</p><p>Hardware, Intel ITX 1.2GHz Celeron, 1Gb memory, 4Gb SSD drive, TDM800P(4 FXS, 4FXO)</p> ]]></content:encoded> </item> <item><title>By: Ram Mohan</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-168336</link> <dc:creator>Ram Mohan</dc:creator> <pubDate>Mon, 17 Jan 2011 10:50:57 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-168336</guid> <description>edit fstab,  try ext3 with mount options  errors=continue,barrier=0   for /
reboot and see...</description> <content:encoded><![CDATA[<p>edit fstab,  try ext3 with mount options  errors=continue,barrier=0   for /<br
/> reboot and see&#8230;</p> ]]></content:encoded> </item> <item><title>By: sathishkumar</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-161493</link> <dc:creator>sathishkumar</dc:creator> <pubDate>Thu, 25 Nov 2010 12:10:33 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-161493</guid> <description>Due to server improper shut down or hang up that time the sectors may corrupt. When the system use the corrupted sector. The machine will go to readonly format.</description> <content:encoded><![CDATA[<p>Due to server improper shut down or hang up that time the sectors may corrupt. When the system use the corrupted sector. The machine will go to readonly format.</p> ]]></content:encoded> </item> <item><title>By: Santhosh</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-159973</link> <dc:creator>Santhosh</dc:creator> <pubDate>Fri, 01 Oct 2010 09:41:16 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-159973</guid> <description>Hi Greg,
As you told &quot;This is a bug in the Linux kernel  and it is fixed in kernels as of 2.6.22&quot;, I would like to know what exactly the problem is i.e. which scenario would have caused file system to become readonly.
We are currently using kernel version 2.6.10 and we are facing same problem. I would like to know what exactly the fix done in 2.6.22(files modified). So that i can go through the same file and incorporate same in our kernel.</description> <content:encoded><![CDATA[<p>Hi Greg,<br
/> As you told &#8220;This is a bug in the Linux kernel  and it is fixed in kernels as of 2.6.22&#8243;, I would like to know what exactly the problem is i.e. which scenario would have caused file system to become readonly.<br
/> We are currently using kernel version 2.6.10 and we are facing same problem. I would like to know what exactly the fix done in 2.6.22(files modified). So that i can go through the same file and incorporate same in our kernel.</p> ]]></content:encoded> </item> <item><title>By: Touhid</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-154698</link> <dc:creator>Touhid</dc:creator> <pubDate>Fri, 02 Apr 2010 10:46:30 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-154698</guid> <description>I have corrected above problem with fsck, e2fsck.
go with &quot;linux rescue&quot; and repair sectors.</description> <content:encoded><![CDATA[<p>I have corrected above problem with fsck, e2fsck.<br
/> go with &#8220;linux rescue&#8221; and repair sectors.</p> ]]></content:encoded> </item> <item><title>By: Hari</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-153506</link> <dc:creator>Hari</dc:creator> <pubDate>Sat, 13 Feb 2010 11:06:21 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-153506</guid> <description>Please give me step by step instructions...
Help me dudes...................</description> <content:encoded><![CDATA[<p>Please give me step by step instructions&#8230;</p><p> Help me dudes&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.</p> ]]></content:encoded> </item> <item><title>By: Sam Jas</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-151856</link> <dc:creator>Sam Jas</dc:creator> <pubDate>Thu, 26 Nov 2009 07:42:13 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-151856</guid> <description>Hi All,
I am frequently getting read-only file system error on my server.
We are using postgres, Grid database. The size of database is very huge.
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 &quot;read only file system&quot; , 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.</description> <content:encoded><![CDATA[<p>Hi All,<br
/> I am frequently getting read-only file system error on my server.<br
/> We are using postgres, Grid database. The size of database is very huge.<br
/> CentOS 5.3 64 bit Areca high point rocket raid 3520 8 port<br
/> 32 GB RAM<br
/> Assemble hardware.<br
/> 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<br
/> are getting errors like &#8220;read only file system&#8221; , 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.</p><p>I will appreciate you if somebody help me to get rid out of this issue.</p> ]]></content:encoded> </item> <item><title>By: joseph</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-150841</link> <dc:creator>joseph</dc:creator> <pubDate>Sun, 27 Sep 2009 11:23:36 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-150841</guid> <description>To become Read-only is much better than damaging the filesystem. Then what you need to do is to backup the partition followed by a fsck.</description> <content:encoded><![CDATA[<p>To become Read-only is much better than damaging the filesystem. Then what you need to do is to backup the partition followed by a fsck.</p> ]]></content:encoded> </item> <item><title>By: Fahdi</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-147076</link> <dc:creator>Fahdi</dc:creator> <pubDate>Fri, 06 Feb 2009 20:59:28 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-147076</guid> <description>@Erik
Dude you are great you saved me to reinstall OS. Great I fixed my OS.
Thank Alot.
Regards,</description> <content:encoded><![CDATA[<p>@Erik<br
/> Dude you are great you saved me to reinstall OS. Great I fixed my OS.</p><p>Thank Alot.</p><p>Regards,</p> ]]></content:encoded> </item> <item><title>By: Rajagopal</title><link>http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-146718</link> <dc:creator>Rajagopal</dc:creator> <pubDate>Thu, 15 Jan 2009 13:35:00 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/linux-filesytem-goes-read-only.html#comment-146718</guid> <description>This saved my day. I spent the last four hours trying to figure out why I always ended up in a readonly mode when boot failed. Thanks for sharing the info.</description> <content:encoded><![CDATA[<p>This saved my day. I spent the last four hours trying to figure out why I always ended up in a readonly mode when boot failed. Thanks for sharing the info.</p> ]]></content:encoded> </item> </channel> </rss>
