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).
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.
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, 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.
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
