Package: e2fsprogs
Version: 1.41.9-1
Severity: important
fsck.ext3 enforces synchronized clocks, but does not pull anything in to
actually make sure that they are.
| Checking root file system...fsck from util-linux-ng 2.16.1
| /dev/xvda: Superblock last write time (Mon Nov 23 12:55:16 2009,
| now = Mon Nov 23 12:54:14 2009) is in the future.
|
|
| /dev/xvda: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
| (i.e., without -a or -p options)
| fsck died with exit status 4
In most virtualized environments the clock is set from the host on
startup but independent after that.
Because this can also happen easily for the _supported_ configuration
with a system clock saved in local time (see /etc/defaults/rcS), I
though about considering this as breaks the whole system.
Bastian
--
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
