On Thu, Apr 30, 2015 at 5:11 PM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > On Thu, 2015-04-30 at 19:45 -0400, Felix Miata wrote: >> Adam Williamson composed on 2015-04-30 16:37 (UTC-0700): >> >> > I'd prefer objective analysis over anecdata. poettering's >> > contention >> > is : >> >> > i) there is only a problem if you have time-based fsck enabled >> > ii) this is not the default >> >> > your anecdote does not provide enough information to prove or >> > disprove >> > his contention. >> >> 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 $ sudo tune2fs -l [my ext4 root device] ... Mount count: 7 Maximum mount count: 21 Last checked: Mon Apr 6 10:42:37 2015 Check interval: 15552000 (6 months) Next check after: Sat Oct 3 10:42:37 2015 ... This filesystem has survived several Fedora upgrades, but I'm pretty sure I created it with mke2fs on some Fedora version. This suggests that time-based fsck is or was default-enabled at some point. --Andy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
