aboutsummaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorEric Sandeen <sandeen@redhat.com>2011-02-17 15:55:15 -0600
committerTheodore Ts'o <tytso@mit.edu>2011-02-20 20:45:12 -0500
commit3daf592646b668133079e2200c1e776085f2ffaf (patch)
treeece1a205bdd6ac37633934c9497c2900bef893b2 /tests
parentb6d274f7c67333e9d4b191b0d27a00be6a2d723f (diff)
downloade2fsprogs-3daf592646b668133079e2200c1e776085f2ffaf.tar.gz
e2fsprogs-3daf592646b668133079e2200c1e776085f2ffaf.tar.xz
e2fsprogs-3daf592646b668133079e2200c1e776085f2ffaf.zip
e2fsprogs: turn off enforced fsck intervals by default
The forced fsck often comes at unexpected and inopportune moments, and even enterprise customers are often caught by surprise when this happens. Because a filesystem with an error condition will be marked as requiring fsck anyway, I submit that the time-based and mount-based checks are not particularly useful, and that administrators can schedule fscks on their own time, or tune2fs the enforced intervals if they so choose. This patch disables the intervals by default, and I've added a new mkfs.conf option to turn on the old behavior of random, unexpected, time-consuming fscks at boot time. ;) Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'tests')
-rw-r--r--tests/mke2fs.conf.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/mke2fs.conf.in b/tests/mke2fs.conf.in
index 99eb75f4..cdb6c952 100644
--- a/tests/mke2fs.conf.in
+++ b/tests/mke2fs.conf.in
@@ -3,6 +3,7 @@
blocksize = 4096
inode_size = 256
inode_ratio = 16384
+ enable_periodic_fsck = true
lazy_itable_init = false
[fs_types]