On Sat, Aug 08, 2009 at 09:13:32AM -0400, Theodore Tso wrote: > On Sat, Aug 08, 2009 at 02:28:56PM +0200, Wouter Verhelst wrote: > > 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). > > Well, the "last mount time is in the future" logic is the same for > both ext3 and ext4; in fact it's exactly the same code, same program > (e2fsck).
Mm. Perhaps the problem then isn't in e2fsck, but in the kernel that's corrupting the timestamp under certain situations? (this is an utterly wild guess; I would in fact be surprised if this were the case. FWIW, kernel is Debian-provided 2.6.30; 2.6.30-5 at this moment, though it's obviously seen some updates since this first appeared) > The "last mount time in the future" means that the time when e2fsck > was running is less than the time recorded as the "last mount" time in > the superblock. And since your original bug report stated that: > > 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. > > .... I don't see how it can be anything other than a time problem at > boot. Right. Yet, I can only say that from where I'm standing, by (repeatedly) looking at the symptoms, this doesn't appear to be the case. Obviously, one of us is wrong ;-) > Maybe I should extend the error message to print the time in the > superblock and the current time, since there seem to be so many people > who have problems with this, That could indeed be a good idea. > but for now, all I can tell you is to try to reproduce this, and then > check the system time when it dumps you into the root shell, and to > grab the last mount and last write times out of the superblock using > dumpe2fs. Yes, I'll try that. If there is anything else you might want me to look at that could help pinpoint the root of the issue, let me know and I'll be happy to try. -- 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
