On Thu, Aug 06, 2009 at 10:23:55AM +0200, Wouter Verhelst wrote:
> Package: e2fsprogs
> Version: 1.41.8-2
> Severity: normal
> File: /sbin/e2fsck
>
> Due to an incorrect assumption about user interface by the manufacturer,
> my laptop has its 'power almost out' LED hidden somewhere to the left,
> where it cannot be seen unless I turn it almost 90 degrees. Since I
> don't like most of the 'power manager' thingies out there (they all want
> to manage my CPU frequency settings and suspend state too, which I will
> manage myself, thank you very much), I'm not running any, which
> inevitably means that from time to time, the battery runs out.
>
> 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.
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.
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
