From 52889b2323e4dea658006e161d6d95829cca4bfa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= <ludo@gnu.org>
Date: Tue, 12 May 2009 17:46:51 +0000
Subject: [PATCH] Run `fsck' when on AC power.

In practice, it should only run once in a while, and should help
find inconsistencies or corruptions sooner.

See https://mail.cs.uu.nl/pipermail/nix-dev/2009-February/001827.html
for a discussion.


svn path=/nixos/trunk/; revision=15577
---
 boot/boot-stage-1-init.sh | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/boot/boot-stage-1-init.sh b/boot/boot-stage-1-init.sh
index b3b2292beaac..524735b1ba26 100644
--- a/boot/boot-stage-1-init.sh
+++ b/boot/boot-stage-1-init.sh
@@ -166,15 +166,6 @@ checkFS() {
     # Only check block devices.
     if ! test -b "$device"; then return 0; fi
 
-    # For unclean ext3 file systems, fsck.ext3 should just replay the
-    # journal and exit, but in practice this takes *much* longer than
-    # letting the kernel recover the FS.  So, don't run fsck on
-    # journalling file systems.
-    eval $(fstype "$device")
-    if test "$FSTYPE" = ext3 -o "$FSTYPE" = ext4 -o "$FSTYPE" = reiserfs -o "$FSTYPE" = xfs -o "$FSTYPE" = jfs; then
-        return 0;
-    fi
-    
     # Don't run `fsck' if the machine is on battery power.  !!! Is
     # this a good idea?
     if ! onACPower; then