From: Eric Sandeen <sandeen@redhat.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Cc: "Lukáš Czerner" <lczerner@redhat.com>
Subject: [PATCH] tune2fs: remove dire warning about check intervals
Date: Tue, 18 Jul 2017 16:10:49 -0500 [thread overview]
Message-ID: <ce6bff3e-49f4-2bed-67ce-a7be604ce1cf@redhat.com> (raw)
Time & mount-count based checks have been off by default for quite some
time now, but the dire warning about disabling them remains in the
tune2fs manpage, which is confusing. We did "strongly consider
the consequences" and disabled it by default, no need to scare the
user about it now.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/misc/tune2fs.8.in b/misc/tune2fs.8.in
index 5c885f9..a8cacc7 100644
--- a/misc/tune2fs.8.in
+++ b/misc/tune2fs.8.in
@@ -134,17 +134,6 @@ Staggering the mount-counts at which filesystems are forcibly
checked will avoid all filesystems being checked at one time
when using journaled filesystems.
.sp
-You should strongly consider the consequences of disabling
-mount-count-dependent checking entirely. Bad disk drives, cables,
-memory, and kernel bugs could all corrupt a filesystem without
-marking the filesystem dirty or in error. If you are using
-journaling on your filesystem, your filesystem will
-.B never
-be marked dirty, so it will not normally be checked. A
-filesystem error detected by the kernel will still force
-an fsck on the next reboot, but it may already be too late
-to prevent data loss at that point.
-.sp
See also the
.B \-i
option for time-dependent checking.
next reply other threads:[~2017-07-18 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:10 Eric Sandeen [this message]
2017-07-18 22:28 ` [PATCH] tune2fs: remove dire warning about check intervals Andreas Dilger
2017-07-19 1:15 ` Theodore Ts'o
2017-07-19 7:21 ` Lukas Czerner
2017-07-19 14:42 ` Theodore Ts'o
2017-07-20 8:57 ` Lukas Czerner
2017-07-19 17:57 ` Darrick J. Wong
2017-07-19 2:06 ` Eric Sandeen
2017-07-19 7:25 ` Lukas Czerner
2017-07-19 17:26 ` [PATCH V2] tune2fs: edit " Eric Sandeen
2017-07-19 17:29 ` Andreas Dilger
2017-07-23 22:36 ` [V2] " Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce6bff3e-49f4-2bed-67ce-a7be604ce1cf@redhat.com \
--to=sandeen@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).