No, I don't think it's an e2fsprogs issue. It looks like it's an init scripts issue. Fsck should always run on boot, regardless of whether or not /forcefsck is set. What forcefsck should do is set the -f flag, to request a forced check even though the file system appears clean.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692355 Title: fsck doesn't update system info on login -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
