On Sat, 2009-10-10 at 16:28 +0000, Alexander Gitter wrote:
> I'm getting the same behavior as described by
> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/427822/comments/23.
>
> - running Karmic in VirtualBox 3.0.8
> - /proc/version_signature: Ubuntu 2.6.31-13.43-generic
> - my timezone is Europe/Berlin (currently GMT+2)
>
> /dev/sda1: Superblock last mount time (Sat Oct 10 20:00:26 2009, now =
> Sat Oct 10 18:05:13 2009) is in the future.
>
> Where "now" (18:05:13) is the correct time.
> The error can indeed be triggered by just installing available updates through update-manager.
>
*sigh*
If "now" is correct, why would the last mount time be incorrect?
Was this the second time you booted the machine, or a different?
The bit about installing updates intrigues me, you're saying that
updates result in this happening on the next reboot?
Scott
--
Scott James Remnant
<email address hidden>
On Sat, 2009-10-10 at 16:28 +0000, Alexander Gitter wrote:
> I'm getting the same behavior as described by /bugs.launchpad .net/ubuntu/ +source/ e2fsprogs/ +bug/427822/ comments/ 23. signature: Ubuntu 2.6.31- 13.43-generic
> https:/
>
> - running Karmic in VirtualBox 3.0.8
> - /proc/version_
> - my timezone is Europe/Berlin (currently GMT+2)
>
> /dev/sda1: Superblock last mount time (Sat Oct 10 20:00:26 2009, now =
> Sat Oct 10 18:05:13 2009) is in the future.
>
> Where "now" (18:05:13) is the correct time.
> The error can indeed be triggered by just installing available updates through update-manager.
>
*sigh*
If "now" is correct, why would the last mount time be incorrect?
Was this the second time you booted the machine, or a different?
The bit about installing updates intrigues me, you're saying that
updates result in this happening on the next reboot?
Scott
--
Scott James Remnant
<email address hidden>