On Mon, 28 Nov 2016, Michael Biebl wrote:
Oh, this is quite simple to explain.
If your file system is clean, fsck will simply do nothing.
The "Last checked" attribute is only reset, if fsck is actually run due to
1/ unclean file system
2/ forced fsck (fsck.mode=force on the kernel command line)
3/ max mount count or check interval reached.
that's clear now, but was not really obvious: syslog tells when fsck is
launched, and tune2fs when it did something. I checked that it's true
not only for /, but for other partitions too.
It seems that one must not be too curious, as each time you dig too
deep, you find some kind of mystery. Last example: looking at syslog, I
found some sequences repeated 10 to 12 times in 1 minute, like:
Mounted /d2.
Mounted /d5.
Mounted /d3.
Mounted /we.
Mounted /data.
Mounted /.
Mounted /w.
or
Started File System Check on /dev/sda3.
Started File System Check on
/dev/disk/by-uuid/70d8e3f7-010d-4a11-b265-5727509735ed.
Started File System Check on
/dev/disk/by-uuid/60c4562b-9c8f-4e82-ae58-2db298bc0a43.
Starting File System Check on
/dev/disk/by-uuid/9abca58e-191a-4894-98cf-a87e59569038...
Started File System Check on
/dev/disk/by-uuid/9abca58e-191a-4894-98cf-a87e59569038.
best regards,
--
Pierre Frenkiel
