I second that, I can understand the behaviour on servers or other mission critical systems, but there seems to be no point forcing an fsck for such an issue on either desktops or mobile systems. Would be cool to be able to enable/disable this feature with a mount option (eg. mount=ignore_superbock_timestamp,defaults).
-- superblock last write time is in the future https://bugs.launchpad.net/bugs/268808 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
