On Thu, Aug 06, 2009 at 06:13:29AM -0400, Theodore Tso wrote: > On Thu, Aug 06, 2009 at 10:23:55AM +0200, Wouter Verhelst wrote: > > When this happens, on reboot, the system always complains that the > > superblock of my / filesystem (an ext4 one) has its last mount count in > > the future, which is an 'unexpected inconsistency' and causes it to drop > > to a root login, asking me to perform a manual fsck. > > > > Since this happens every time, I think the 'unexpected' part of the > > above is a bug, and an annoying one at that. > > E2fsck requires that the system clock be correct when it runs. I bet > your trashy laptop not only has a bad design where you don't notice > that you are running out of memory, but also that it doesn't have a > separate CMOS to maintain your CMOS memory and time-of-day clock after > your primary battery has died. As a result, when you restore power to > your laptop and reboot, I suspect what is happening is that your > time-of-day clock is insane at the time when e2fsck is running, and so > it's deciding that it needs to do a full check of the filesystem due > to it being too long since the last time the filesystem was checked, > or some such.
That was my first thought. However, I consider this unlikely, given: - The problem did not happen when I was running the system off of ext3 rather than ext4 (at least, I do not remember that to be the case). - I filed this bug report while on the train, after it had just happened. I did not have network there, so it was not a matter of the system clock being wildly incorrect and me not noticing because NTP fixed my clock before I could log on, or some such. > What message is e2fsck printing to explain why it thinks a full > filesystem check is warranted? I'm almost 99% certain it's > time-related. There is no message other than the 'UNEXPECTED INCONSISTENCY' message. The check is the normal 'fsck -a' check that is done at bootup, which finds that error and tells me to fix it. -- The biometric identification system at the gates of the CIA headquarters works because there's a guard with a large gun making sure no one is trying to fool the system. http://www.schneier.com/blog/archives/2009/01/biometrics.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
