On Tue, Apr 02, 2019 at 07:43:34PM -0700, Elliott Mitchell wrote:
> Package: e2fsprogs
> Version: 1.43.4-2
>
> Could `mke2fs` and `tune2fs` get some method to initialize the maximum
> mount count to a non-zero value?
>
> Having to search for random values to initialize the maximum mount count
> is a bit annoying. Perhaps a -O init_max_mount_count setting?
>
> I understand the author's misgivings about all the complaints from people
> annoyed by precautionary checks. Yet some of us are fine with occasional
> checks. Meanwhile the time-based checks were just awful.
I suspect the best way forward is to teach tune2fs to be able to
support "tune2fs -c random". The -O option is only for file system
features that are encoded in feature bitmaps in the ext4 superblock.
However, if you are using LVM, the better way to move forward is to
use e2scrub, which is in e2fsprogs 1.45.0. That's not going to land
in Debian Buster, since we're in lockdown and the version of e2fsprogs
in Buster is 1.44.5-1. But realistically, the change that you are
asking for isn't going to be landing any time soon, either.
- Ted
