cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lsimons <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-7143: Refactoring of the syste...
Date Mon, 22 Sep 2014 14:54:59 GMT
Github user lsimons commented on the pull request:
    thanks for testing rohit. We've never seen this (with xen).
    If you look at the error,
    /dev/vda5: Superblock last mount time (Fri Sep 19 14:54...)
       now = Mon Sep 15 20:34... is in the future
    the fsck is unhappy with the last recorded mount being sep 19 (last friday, which is correct,
i.e. it matches with when we ran the build on jenkins) because the date of the system as its
booting is in the past, sep 15. So somehow the system clock of the VM is wrong...?
    Either during the build process the time was moved backward some time after mounting the
filesystem, or during the boot process time moved backward, or ... ?
    I've checked and the date of the build slave where the image was baked is correct and
managed with ntp so very likely was always I really don't see how the build could
result in that timestamp existing anywhere.
    Can you check the date of your KVM host? Or perhaps if you have an NTP server with a wrong

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message