Blame SOURCES/e2fsprogs-1.43.4-tune2fs-edit-dire-warning-about-check-intervals.patch

0ef434
From 2f121a201133bf6b8efeda5d898c938d12bd6f65 Mon Sep 17 00:00:00 2001
0ef434
From: Eric Sandeen <sandeen@redhat.com>
0ef434
Date: Sun, 23 Jul 2017 18:34:57 -0400
0ef434
Subject: [PATCH] tune2fs: edit dire warning about check intervals
0ef434
0ef434
Time & mount-count based checks have been off by default for quite some
0ef434
time now, but the dire warning about disabling them remains in the
0ef434
tune2fs manpage, which is confusing.  We did "strongly consider
0ef434
the consequences" and disabled it by default, no need to scare the
0ef434
user about it now.  Inform the user of the consequences in a more
0ef434
measured tone.
0ef434
0ef434
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
0ef434
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
0ef434
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
0ef434
---
0ef434
 misc/tune2fs.8.in | 15 ++++++---------
0ef434
 1 file changed, 6 insertions(+), 9 deletions(-)
0ef434
0ef434
diff --git a/misc/tune2fs.8.in b/misc/tune2fs.8.in
0ef434
index e07da28..8949f64 100644
0ef434
--- a/misc/tune2fs.8.in
0ef434
+++ b/misc/tune2fs.8.in
0ef434
@@ -122,7 +122,9 @@ Staggering the mount-counts at which filesystems are forcibly
0ef434
 checked will avoid all filesystems being checked at one time
0ef434
 when using journaled filesystems.
0ef434
 .sp
0ef434
-You should strongly consider the consequences of disabling
0ef434
+Mount-count-dependent checking is disabled by default to avoid
0ef434
+unanticipated long reboots while e2fsck does its work.  However,
0ef434
+you may wish to consider the consequences of disabling
0ef434
 mount-count-dependent checking entirely.  Bad disk drives, cables,
0ef434
 memory, and kernel bugs could all corrupt a filesystem without
0ef434
 marking the filesystem dirty or in error.  If you are using
0ef434
@@ -277,15 +279,10 @@ as months, and
0ef434
 .B w
0ef434
 as weeks.  A value of zero will disable the time-dependent checking.
0ef434
 .sp
0ef434
-It is strongly recommended that either
0ef434
+There are pros and cons to disabling these periodic checks; see the
0ef434
+discussion under the
0ef434
 .B \-c
0ef434
-(mount-count-dependent) or
0ef434
-.B \-i
0ef434
-(time-dependent) checking be enabled to force periodic full
0ef434
-.BR e2fsck (8)
0ef434
-checking of the filesystem.  Failure to do so may lead to filesystem
0ef434
-corruption (due to bad disks, cables, memory, or kernel bugs) going
0ef434
-unnoticed, ultimately resulting in data loss or corruption.
0ef434
+(mount-count-dependent check) option for details.
0ef434
 .TP
0ef434
 .B \-j
0ef434
 Add an ext3 journal to the filesystem.  If the 
0ef434
-- 
0ef434
2.7.5
0ef434