<?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: file corruption in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221397#M51691</link>
    <description>Cause? I'd say that would be the improper shutdown.&lt;BR /&gt;&lt;BR /&gt;Did fsck run at boot? If not, unmount the filesystem and run it to verify it's integrity.</description>
    <pubDate>Mon, 25 Jan 2010 12:53:57 GMT</pubDate>
    <dc:creator>J. Maestre</dc:creator>
    <dc:date>2010-01-25T12:53:57Z</dc:date>
    <item>
      <title>file corruption</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221396#M51690</link>
      <description>HI ALL&lt;BR /&gt;&lt;BR /&gt;Recently some linux files are corrupted, files are sysctl.conf and odbc.ini.   &lt;BR /&gt;&lt;BR /&gt;ACtually my end improper shutdown happend, once power  came system rebooted but at some stage power trip happend.&lt;BR /&gt;&lt;BR /&gt;What might be cause these files corrupted means inside contents are improper arrangment  thats why applications not running fine.&lt;BR /&gt;&lt;BR /&gt;I want to know what is cause root?</description>
      <pubDate>Mon, 25 Jan 2010 10:45:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221396#M51690</guid>
      <dc:creator>muralikrishna</dc:creator>
      <dc:date>2010-01-25T10:45:59Z</dc:date>
    </item>
    <item>
      <title>Re: file corruption</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221397#M51691</link>
      <description>Cause? I'd say that would be the improper shutdown.&lt;BR /&gt;&lt;BR /&gt;Did fsck run at boot? If not, unmount the filesystem and run it to verify it's integrity.</description>
      <pubDate>Mon, 25 Jan 2010 12:53:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221397#M51691</guid>
      <dc:creator>J. Maestre</dc:creator>
      <dc:date>2010-01-25T12:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: file corruption</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221398#M51692</link>
      <description>Impropoer shutdown can currupt the files that would lead in crashing of server (which is rare in Linux server )so you may need to run fsck to check integrity and/or restore from backup.&lt;BR /&gt;&lt;BR /&gt;BR,&lt;BR /&gt;Kapil+</description>
      <pubDate>Tue, 26 Jan 2010 07:54:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221398#M51692</guid>
      <dc:creator>Kapil Jha</dc:creator>
      <dc:date>2010-01-26T07:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: file corruption</title>
      <link>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221399#M51693</link>
      <description>i got clue</description>
      <pubDate>Thu, 28 Jan 2010 04:57:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/file-corruption/m-p/5221399#M51693</guid>
      <dc:creator>muralikrishna</dc:creator>
      <dc:date>2010-01-28T04:57:04Z</dc:date>
    </item>
  </channel>
</rss>

