From bccb7653e1348e02495218d830588b2cabaacb8b Mon Sep 17 00:00:00 2001
From: Sven Vermeulen <sven.vermeulen@siphos.be>
Date: Sat, 4 Sep 2010 23:45:24 +0200
Subject: [PATCH] unkn

---
 src/linux_sea/13-storagemanagement.xml | 33 ++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/src/linux_sea/13-storagemanagement.xml b/src/linux_sea/13-storagemanagement.xml
index 8f05fdc..f8ddc3e 100644
--- a/src/linux_sea/13-storagemanagement.xml
+++ b/src/linux_sea/13-storagemanagement.xml
@@ -471,6 +471,39 @@ Changed system type of partition 4 to 82 (Linux swap)</programlisting>
         your file system. This has already been covered in <xref
         linkend="mountsection" />.</para>
       </section>
+
+      <section>
+        <title>Fixing Corrupt File Systems</title>
+
+        <para>If a file system is corrupt, you will notice this when you want
+        to mount the file system (or when the system tries to automatically
+        mount the file system for you):</para>
+
+        <programlisting>/dev/hda4:
+The superblock could not be read or does not describe a correct ext2
+filesystem. If the device is valid and it really contains an ext2
+filesystem (and not swap or ufs or something else), the the superblock
+is corrupt, and you might try running e2fsck with an alternate superblock:
+         e2fsck -b 8193 &lt;device&gt;
+
+* Filesystem couldn't be fixed :(</programlisting>
+
+        <para>Now, before you run into the night, screaming for help, sit down
+        and try executing the command that the output gave:</para>
+
+        <programlisting>(The proposed command will vary depending on file system used)
+~# <command>e2fsck -b 8193 /dev/hda4</command></programlisting>
+
+        <para>If the <command>e2fsck</command><indexterm>
+            <primary>e2fsck</primary>
+          </indexterm> check reports that there is corruption found, it might
+        ask you to confirm every correction it wants to do. As a file system
+        check can easily report hundreds to thousands of corruptions (not that
+        that means that there are thousands of files corrupt), it might be
+        easier to tell e2fsck to just acknowledge them all for you:</para>
+
+        <programlisting>~# <command>e2fsck -y /dev/hda4</command></programlisting>
+      </section>
     </section>
   </section>