[Bug 1201978] dracut assumes BIOS time is UTC closed without fixing again

[Eric Sandeen]

On 4/30/15 7:35 PM, Felix Miata wrote:
> Adam Williamson composed on 2015-04-30 17:11 (UTC-0700):
> 
>>> He never mentioned what time-based fsck is that I saw,
> 
>> "What doesn't work is rtc-in-local in early-boot, that's all. And that
>> doesn't matter really, except if you are crazy enough to manually
>> enable time-based fsck in ext234, which has been turned off by default
>> in fedora since time begain, and even has been turned off upstream
>> now, because it's simply a crazy feature." - Lennart, yesterday: 
>> https://lists.fedoraproject.org/pipermail/devel/2015-April/210282.html
> 
> I saw that. It didn't tell me anything I understood, since I don't know what
> time-based fsck is, or more particularly, what enables or disables it, and so
> unlikely myself made any changes in recent weeks or months to cause the
> current boot delays these fscks consistently impose.

well, not since time began; it was 1.42-ish:

commit 3daf592646b668133079e2200c1e776085f2ffaf
Author: Eric Sandeen <sandeen at redhat.com>
Date:   Thu Feb 17 15:55:15 2011 -0600

    e2fsprogs: turn off enforced fsck intervals by default
    
    The forced fsck often comes at unexpected and inopportune moments,
    and even enterprise customers are often caught by surprise when
    this happens.  Because a filesystem with an error condition will
    be marked as requiring fsck anyway, I submit that the time-based
    and mount-based checks are not particularly useful, and that
    administrators can schedule fscks on their own time, or tune2fs
    the enforced intervals if they so choose.  This patch disables the
    intervals by default, and I've added a new mkfs.conf option to
    turn on the old behavior of random, unexpected, time-consuming
    fscks at boot time.  ;)
    
    Signed-off-by: Eric Sandeen <sandeen at redhat.com>
    Signed-off-by: Theodore Ts'o <tytso at mit.edu>

(some of us are old enough that our time began before 2011) ;)

Time-based check is ext234's (old default) behavior of forcing a full
fsck just because X days or Y mounts have gone by.

Any filesystem created prior to the above would have these time-based
or mount-based checks enabled by default.

You can see if it's set on your fs by looking at dumpe2fs, i.e.:

# dumpe2fs -h /dev/md0 | grep -i "mount count\|Check interval\|check after"
dumpe2fs 1.41.12 (17-May-2010)
Mount count:              24
Maximum mount count:      21
Check interval:           15552000 (6 months)
Next check after:         Fri Aug  2 15:55:32 2013

-Eric