On 4/30/15 7:58 PM, Matthew Miller wrote:
On Thu, Apr 30, 2015 at 05:22:20PM -0700, Andrew Lutomirski wrote:
> Maximum mount count: 21
> Last checked: Mon Apr 6 10:42:37 2015
> Check interval: 15552000 (6 months)
The default is definely now 0, but you're right, if you've upgraded for
a long time, it won't be changed. (You can change it now with tune2fs,
though, if you want.)
Also, the e2fsck.conf man page suggests that the program has "some
heuristics that assume that the system clock is correct" — I'm not sure
without checking the code if the check interval is really the only one.
But you might consider setting the `broken_system_clock` option in
/etc/e2fsck.conf.
Hmmm, in fact, maybe we should consider this the _default_ (at least
for workstation and desktop spins).
It was/is set as default, and then time-based checks never fired.
So we un-defaulted it, and then hit this stuff.
Such a mess. :(
I need to get 1202024 resolved, ted checked in a version of a patch
I proposed to try to resolve some of this.
http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?id=f096708126412...
I'll get that pushed to testing tonight, sorry for being slow with it.
-Eric