Endolith, That's what we do. The problem is that the system clock is set incorrectly thanks to Ubuntu's decision at the time when the file system is mounted. This means that the incorrect system time is set at mount time. The time then gets warped into the past (to the correct time) later by other init scripts, perhaps when ntpdate is run. So checking to see if the mounted has been mounted since the last time it has been checked from problem only works if the system clock is reliable --- which it isn't if your system clock ticks localtime, and either (a) the init scripts are buggy, or (b) the system doesn't know what timezone it's in, because the Ubuntu installer doesn't want to ask the users.
This lead to me repeated having to explain this to Ubuntu users again, and again, and again, and how this wasn't e2fsck's fault, since there was no way I could tell whether or not this was due to filesystem bugs, or a buggy init scripts. Hence the buggy init scripts config option. In any case, I've confirmed that this is precisely why this bug is happening. -- resize2fs doesn't notice the partition was fsck'ed https://bugs.launchpad.net/bugs/373409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
