<?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: Ext3 error on RedHat 4.0 AS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736138#M21887</link>
    <description>Hi Dudes, I see alot of reports on ext3 - mounting read-only on the net. But wondering n need to know wht is actually causing it. That worry me alot man. Solution of fsck is fine. But is the sudden readonly that is not HEALTHY and RISKY. Data will just be GONE if fsck fails. Any pre-emptive measures? Was thinking of logging redhat a call. Cliff</description>
    <pubDate>Tue, 21 Feb 2006 13:06:16 GMT</pubDate>
    <dc:creator>Cliff Lim Kok Hwee</dc:creator>
    <dc:date>2006-02-21T13:06:16Z</dc:date>
    <item>
      <title>Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736136#M21885</link>
      <description>Hi Forum,&lt;BR /&gt;&lt;BR /&gt;I recently untar 1 filesystem from 1 server into another server running RedHat 4.0 AS. This houses Oracle Application.&lt;BR /&gt;&lt;BR /&gt;Recently, was encountered the following errors:&lt;BR /&gt;&lt;BR /&gt;- EXT3-fs error (device md5): ext3_free_blocks_sb: bit already cleared for block 1303980 Aborting journal on device md5. ext3_abort called. EXT3-fs error (device md5): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only &lt;BR /&gt;&lt;BR /&gt;Only way was reboot the server and then it become ok. On my scenerio, the filesystem screw up upon a reboot and WE GOT NO BACKUP :)&lt;BR /&gt;&lt;BR /&gt;Need any advise.&lt;BR /&gt;Cliff</description>
      <pubDate>Tue, 21 Feb 2006 11:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736136#M21885</guid>
      <dc:creator>Cliff Lim Kok Hwee</dc:creator>
      <dc:date>2006-02-21T11:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736137#M21886</link>
      <description>Your md device is IDE or SCSI? A reboot may clean the filesystem if a fsck was runned. You should force a fsck to check for file system inconsistences.</description>
      <pubDate>Tue, 21 Feb 2006 12:39:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736137#M21886</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-02-21T12:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736138#M21887</link>
      <description>Hi Dudes, I see alot of reports on ext3 - mounting read-only on the net. But wondering n need to know wht is actually causing it. That worry me alot man. Solution of fsck is fine. But is the sudden readonly that is not HEALTHY and RISKY. Data will just be GONE if fsck fails. Any pre-emptive measures? Was thinking of logging redhat a call. Cliff</description>
      <pubDate>Tue, 21 Feb 2006 13:06:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736138#M21887</guid>
      <dc:creator>Cliff Lim Kok Hwee</dc:creator>
      <dc:date>2006-02-21T13:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736139#M21888</link>
      <description>- do you see something interesting in "dmesg" output and/or into /var/log/messages?&lt;BR /&gt;- what do you see under  /proc/mdstat?</description>
      <pubDate>Tue, 21 Feb 2006 16:15:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736139#M21888</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2006-02-21T16:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736140#M21889</link>
      <description>log a call with RH. if you paid for their support, you can't get any better then that.</description>
      <pubDate>Wed, 22 Feb 2006 01:53:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736140#M21889</guid>
      <dc:creator>dirk dierickx</dc:creator>
      <dc:date>2006-02-22T01:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ext3 error on RedHat 4.0 AS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736141#M21890</link>
      <description>get a copy of ubuntu or knoppix Live CD and dd your current drives to new media...  don't do anything else until you get a backup...</description>
      <pubDate>Wed, 22 Feb 2006 10:27:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ext3-error-on-redhat-4-0-as/m-p/3736141#M21890</guid>
      <dc:creator>Alan_152</dc:creator>
      <dc:date>2006-02-22T10:27:25Z</dc:date>
    </item>
  </channel>
</rss>

