<?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 Having to e2fsck manually in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/having-to-e2fsck-manually/m-p/2786493#M2217</link>
    <description>All,&lt;BR /&gt;I am sure on some occasion you have experience a hard-reboot. Sometimes a hard re-boot requires manual intervention with e2fsck. How does one properly do this w/o risking corrution when the file system you need to do this on is root and it's mounted? e.g: When I get this prompt "crontrol D to reboot or enter root's password for maintanence", I usually enterl root's password and clean the root filesystme with "/sbin/e2fsck -y -b 32768 /dev/hda2". Is this way to do it? or is there a better of doing this w/o risking file system corruption? Thanks.</description>
    <pubDate>Wed, 14 Aug 2002 23:58:40 GMT</pubDate>
    <dc:creator>K.C. Chan</dc:creator>
    <dc:date>2002-08-14T23:58:40Z</dc:date>
    <item>
      <title>Having to e2fsck manually</title>
      <link>https://community.hpe.com/t5/operating-system-linux/having-to-e2fsck-manually/m-p/2786493#M2217</link>
      <description>All,&lt;BR /&gt;I am sure on some occasion you have experience a hard-reboot. Sometimes a hard re-boot requires manual intervention with e2fsck. How does one properly do this w/o risking corrution when the file system you need to do this on is root and it's mounted? e.g: When I get this prompt "crontrol D to reboot or enter root's password for maintanence", I usually enterl root's password and clean the root filesystme with "/sbin/e2fsck -y -b 32768 /dev/hda2". Is this way to do it? or is there a better of doing this w/o risking file system corruption? Thanks.</description>
      <pubDate>Wed, 14 Aug 2002 23:58:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/having-to-e2fsck-manually/m-p/2786493#M2217</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2002-08-14T23:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: Having to e2fsck manually</title>
      <link>https://community.hpe.com/t5/operating-system-linux/having-to-e2fsck-manually/m-p/2786494#M2218</link>
      <description>There is little risk of corrupting the file system &lt;BR /&gt;by running e2fsck.  However it can delete or truncate files&lt;BR /&gt;where the file system information is incomplete.&lt;BR /&gt;&lt;BR /&gt;I would drop the switches and &lt;BR /&gt;run 'e2fsck /dev/hda2'.  This&lt;BR /&gt;will use the default superblock and prompt you&lt;BR /&gt;before any changes.  Add the&lt;BR /&gt;-b 32768 switch if the &lt;BR /&gt;superblock can't be found.&lt;BR /&gt;&lt;BR /&gt;The effects of e2fsck I have &lt;BR /&gt;encountered are:&lt;BR /&gt;- log files truncated in the middle of a record. &lt;BR /&gt;- files being created during shutdown removed. &lt;BR /&gt;- files without a directory entry removed.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Aug 2002 12:53:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/having-to-e2fsck-manually/m-p/2786494#M2218</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2002-08-16T12:53:22Z</dc:date>
    </item>
  </channel>
</rss>

