| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <ce6bff3e-49f4-2bed-67ce-a7be604ce1cf@redhat.com> Date: Tue, 18 Jul 2017 16:10:49 -0500 From: Eric Sandeen <sandeen@...hat.com> To: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org> Cc: Lukáš Czerner <lczerner@...hat.com> Subject: [PATCH] tune2fs: remove dire warning about check intervals 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@...hat.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.
Powered by blists - more mailing lists