Theodore Ts'o wrote... > This was behaviour that was requested per Debian bug #205177[1], and > note that it doesn't skip the checks forever. It just doubles the > check interval (so if check interval is 14 days, it will make it be 28 > days), and if the max_mount_count was 20, it will not wait until the > 40th mount. So it's not "always skipped"; it's rather deferred.
My perception was otherwise but I shouldn't argue without solid proof.
And yes, I am enabling periodic fsck checks, having experienced
corrupted file systems a few times in the past (rather caused by failure
in the underlying block device than by ext4 itself). Migrating to
e2scrub still is something to consider where possible.
Still, I find an "on battery" message disturbing if there isn't any. So,
if I do (some output stripped):
# fallocate --length 128M /tmp/blob
# mkfs.ext4 /tmp/blob
# tune2fs -c 36 -C 35 /tmp/blob
# cat /proc/apm
1.13 1.2 0x02 0xff 0xff 0xff -1% -1 ?
# e2fsck 1.47.2 (5-Feb-2023)
/tmp/blob: clean, 11/32768 files, 13883/131072 blocks (check deferred; on
battery)
^^^^^^^^^^
That's why I'd prefer to derive "on battery" from that APM line only if
and only if APM's "AC line status" is "off-line", and otherwise not. But
I'll leave that to you to decide.
All the best,
Christoph
signature.asc
Description: PGP signature
