package: e2fsprogs
severity: critical
justification: breaks the entire system
When booting my quemu armel system I get the following
Checking root file system...fsck from util-linux-ng 2.16.1
/dev/sda1: Superblock last mount time (Thu Jan 1 01:03:11 1970,
now = Thu Jan 1 01:00:52 1970) is in the future.
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4).
An automatic file system check (fsck) of the root filesystem failed. A
manual fsck must be performed, then the system restarted. The fsck
should be performed in maintenance mode with the root filesystem mounted
in read-only mode. ... failed!
The root filesystem is currently mounted in read-only mode. A
maintenance shell will now be started. After performing system
maintenance, press CONTROL-D to terminate the maintenance shell and
restart the system. ... (warning).
Running fsck manually results in no errors but on rebooting I get the
above again.
It seems that some fairly recent change (I dunno exactly when, since I
boot and update the system infrequently) has turned last mount time in
the future from a warning to an error. This renders any system that does
not have a usable rtc (like the aforementioned qemu armel system)
unbootable.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
