On Sat, 2009-10-10 at 16:28 +, 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 timezo
On Fri, 2009-10-09 at 20:01 +, Dan Kegel wrote:
> /dev/sda1: Superblock last mount time (Fri Oct 9 12:47:47 2009,
> now = Fri Oct 9 :5:54:32 2009) is in the future.
>
> I'm in Los Angeles, UTC+7 or so, so it does seem like a UTC/localtime
> disagreement.)
>
Which of the two was the _
On Thu, 2009-10-01 at 10:31 +, Daniel Fett wrote:
> This is the message I get, running karmic alpha 6 with latest updates,
> after I did a "sudo reboot" in a terminal. Note the different time
> values shown.
>
I would guess that you're in UTC+0200 ?
Most importantly - what *was* the correct
Sébastien Bernard wrote:
> Why not wait until the UTC passed the date of the last write ?
> For gmt+4, is to wait 4hours beforce booting the system again.
> So the condition of the bug won't be present.
> Then update to the correct version.
>
>
I'm not clear what you mean with 'update to the co
On Wed, Sep 16, 2009 at 10:23:30AM -, Steve Langasek wrote:
> Is the e2fsprogs task still relevant, or should it be closed invalid?
It should be closed invalid.
--
fsck says last write time in future
https://bugs.launchpad.net/bugs/427822
You received this bug notification because you are a
