Hi Theodore, I have been running in this same issue lately. The real problem was a new X11 driver which did not work too well with my ATI card, locking the system hard every few minutes.
Why this leads to some timestamp in the super block to be in the future is beyond me. I have to agree though that this is a master PITA. And it's a questionable approach to assume the file system is broken because of some timestamp (after all, the system clock could be wrong just as well). BTW, see also https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/427822 Seems to be caused by a kernel bug. Anyway, I'd still vote against checking the last-mounted time against an unknown time reference. Greetings, Torsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
