<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Suddenly the / filesystem is readonly in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859071#M25105</link>
    <description>This is what disk hardware failure looks like.&lt;BR /&gt;&lt;BR /&gt;Linux kernel can behave in various ways when it detects a disk error that caused data to be lost: it can either panic (=crash) immediately to avoid further damage, keep running but remount the filesystem as read-only, or do nothing special. The default action is to remount the filesystem as read-only. In a critical environment where "server stops at the first sign of trouble" is better than "incomplete or corrupted data", you may want to set the server to panic immediately in situations like this. &lt;BR /&gt;&lt;BR /&gt;If you have anything irreplaceable on the disk (on any filesystem located on that physical disk), backup it *RIGHT NOW*.&lt;BR /&gt;&lt;BR /&gt;When you reboot the server, you can expect at least a full filesystem check, which may take some time and may require some manual actions in single-user mode. Do not trust the disk after that: if the disk surface is physically damaged, there may be loose crumbs of magnetic material moving around inside the disk housing. Over time, the damage can only get worse.&lt;BR /&gt;&lt;BR /&gt;The worst possibility is that the disk may fail its self-diagnostics at the next reboot and be totally unaccessible after that.&lt;BR /&gt;&lt;BR /&gt;Prepare to replace the disk as soon as possible.</description>
    <pubDate>Fri, 08 Sep 2006 04:52:14 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2006-09-08T04:52:14Z</dc:date>
    <item>
      <title>Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859070#M25104</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a SUSE server that was fine until a couple of days.  Suddenly, I cannot create a file or folder in the root filesystem.  I can't even edit.  It says "Read-only file system"&lt;BR /&gt;&lt;BR /&gt;bangpcsl1:~ # mkdir 123&lt;BR /&gt;mkdir: cannot create directory `123': Read-only file system&lt;BR /&gt;&lt;BR /&gt;bangpcsl1:~ # more /etc/SuSE-release&lt;BR /&gt;SUSE LINUX Enterprise Server 9 (i586)&lt;BR /&gt;VERSION = 9&lt;BR /&gt;PATCHLEVEL = 3&lt;BR /&gt;&lt;BR /&gt;Find below the contents of /var/log/messages&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: SCSI error : &amp;lt;0 0 1 0&amp;gt; return code = 0x8000002&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: Info fld=0x6382974, Current sdb: sense key Hardware Error&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: Additional sense: Mechanical positioning error&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: end_request: I/O error, dev sdb, sector 104343923&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: Buffer I/O error on device sdb2, logical block 12779926&lt;BR /&gt;Sep  6 04:25:46 bangpcsl1 kernel: lost page write due to I/O error on sdb2&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: SCSI error : &amp;lt;0 0 1 0&amp;gt; return code = 0x8000002&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: Info fld=0x80c1ecb, Current sdb: sense key Hardware Error&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: Additional sense: Mechanical positioning error&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: end_request: I/O error, dev sdb, sector 135012043&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: Buffer I/O error on device sdb2, logical block 16613441&lt;BR /&gt;Sep  6 04:25:56 bangpcsl1 kernel: lost page write due to I/O error on sdb2&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 kernel: REISERFS: abort (device sdb2): Write error while pushing transaction to disk in flush_journal_list&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 kernel: REISERFS: Aborting journal for filesystem on sdb2&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 kernel: ReiserFS: sdb2: warning: clm-6006: writing inode 152475 on readonly FS&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 last message repeated 5 times&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 kernel: ReiserFS: sdb2: warning: clm-6006: writing inode 57768 on readonly FS&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 last message repeated 5 times&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 kernel: ReiserFS: sdb2: warning: clm-6006: writing inode 152475 on readonly FS&lt;BR /&gt;Sep  6 04:26:58 bangpcsl1 last message repeated 5 times&lt;BR /&gt;&lt;BR /&gt;Please suggest,&lt;BR /&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Sep 2006 01:44:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859070#M25104</guid>
      <dc:creator>GnanaShekar</dc:creator>
      <dc:date>2006-09-08T01:44:40Z</dc:date>
    </item>
    <item>
      <title>Re: Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859071#M25105</link>
      <description>This is what disk hardware failure looks like.&lt;BR /&gt;&lt;BR /&gt;Linux kernel can behave in various ways when it detects a disk error that caused data to be lost: it can either panic (=crash) immediately to avoid further damage, keep running but remount the filesystem as read-only, or do nothing special. The default action is to remount the filesystem as read-only. In a critical environment where "server stops at the first sign of trouble" is better than "incomplete or corrupted data", you may want to set the server to panic immediately in situations like this. &lt;BR /&gt;&lt;BR /&gt;If you have anything irreplaceable on the disk (on any filesystem located on that physical disk), backup it *RIGHT NOW*.&lt;BR /&gt;&lt;BR /&gt;When you reboot the server, you can expect at least a full filesystem check, which may take some time and may require some manual actions in single-user mode. Do not trust the disk after that: if the disk surface is physically damaged, there may be loose crumbs of magnetic material moving around inside the disk housing. Over time, the damage can only get worse.&lt;BR /&gt;&lt;BR /&gt;The worst possibility is that the disk may fail its self-diagnostics at the next reboot and be totally unaccessible after that.&lt;BR /&gt;&lt;BR /&gt;Prepare to replace the disk as soon as possible.</description>
      <pubDate>Fri, 08 Sep 2006 04:52:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859071#M25105</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2006-09-08T04:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859072#M25106</link>
      <description>Hi GnanaShekar,&lt;BR /&gt;&lt;BR /&gt;Looks like you have some hardware issue. &lt;BR /&gt;&lt;BR /&gt;ep 6 04:25:46 bangpcsl1 kernel: SCSI error : &amp;lt;0 0 1 0&amp;gt; return code = 0x8000002&lt;BR /&gt;Sep 6 04:25:46 bangpcsl1 kernel: Info fld=0x6382974, Current sdb: sense key Hardware Error&lt;BR /&gt;&lt;BR /&gt;Check your hard drive "sdb"&lt;BR /&gt;&lt;BR /&gt;Have you tried unmounting the filesystem and ran fsck?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Sathish</description>
      <pubDate>Sat, 09 Sep 2006 03:41:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859072#M25106</guid>
      <dc:creator>sathish kannan</dc:creator>
      <dc:date>2006-09-09T03:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859073#M25107</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Please try the following command which will remount the filesystem in rw&lt;BR /&gt;&lt;BR /&gt;#mount -o remount /&lt;BR /&gt;&lt;BR /&gt;then during maintenance window try the following command to check the disk sdb2 by&lt;BR /&gt;&lt;BR /&gt;#dd if=/dev/sdb2 of=/dev/null&lt;BR /&gt;&lt;BR /&gt;if this output shows any io error problem with you disk.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 11 Sep 2006 00:11:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859073#M25107</guid>
      <dc:creator>Nandu</dc:creator>
      <dc:date>2006-09-11T00:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859074#M25108</link>
      <description>Is it possible you mounted / as an NFS mount point and made a typo? check your /etc/fstab make sure / is not referenced for any mount points on other devices. &lt;BR /&gt;&lt;BR /&gt;Reboot the system.</description>
      <pubDate>Mon, 11 Sep 2006 12:34:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859074#M25108</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2006-09-11T12:34:41Z</dc:date>
    </item>
    <item>
      <title>Re: Suddenly the / filesystem is readonly</title>
      <link>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859075#M25109</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;If a filesystem is no umounted cleanly it can be left dirty and therefore marked in such away that it can not be mounted cleanly rw next boot.&lt;BR /&gt;&lt;BR /&gt;Next boot fsck should fix it though you may need to do this manually in single user mode.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 12 Sep 2006 01:40:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/suddenly-the-filesystem-is-readonly/m-p/3859075#M25109</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-09-12T01:40:15Z</dc:date>
    </item>
  </channel>
</rss>

