perhaps the trigger is when the system boots up with a system time which preceeds the prior bootup. this sort of thing happens because of bug#1335522. and that would explain why it happened this time.
imho such time discrepancy should not trigger full lengthy filesystem checks. i think this should probably be reassigned to fsck.ext2 the attachments were created thusly (the first per request in comment#7): journalctl -b > /tmp/journal.txt grip contigu"|ux.ver" syslog>/tmp/bootups.txt grip is aliased to `zgrep -Ei --colour=always' ** Attachment added: "journalctl -b > /tmp/journal.txt" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1438824/+attachment/4406820/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438824 Title: ALL FSCKs triggered for no apparent reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1438824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
