Плохо курил man tune2fs параметры -c и -i
Эти параметры как раз выкурил в первую очередь:
-c max-mount-counts
Adjust the number of mounts after which the filesystem will be
checked by e2fsck( 8 ). If max-mount-counts is 0 or -1, the num
ber of times the filesystem is mounted will be disregarded by
e2fsck( 8 ) and the kernel.
Staggering the mount-counts at which filesystems are forcibly
checked will avoid all filesystems being checked at one time
when using journaled filesystems.
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 never
be marked dirty, so it will not normally be checked. A filesys
tem 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.
See also the -i option for time-dependent checking.
-C mount-count
Set the number of times the filesystem has been mounted. If set
to a greater value than the max-mount-counts parameter set by
the -c option, e2fsck( 8 ) will check the filesystem at the next
reboot.
-i interval-between-checks[d|m|w]
Adjust the maximal time between two filesystem checks. No post
fix or d result in days, m in months, and w in weeks. A value
of zero will disable the time-dependent checking.
но как понял, там можно только устанавливать значения, а как те, что уже установлены посмотреть?