http://bugs.winehq.org/show_bug.cgi?id=32152
Samuel Nelson valczir.darkvein@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |valczir.darkvein@gmail.com
--- Comment #2 from Samuel Nelson valczir.darkvein@gmail.com 2012-11-07 08:50:06 CST --- I don't think this is a bug. It's pretty common on linux for any large (i.e. more than a few milliseconds) change in the system clock to break your system - the OS generally prefers to blow up instead of reading or writing files that appear to be written in the future.
Have you thought about using a network time program that doesn't make sudden, large adjustments to your time? I use chrony these days, which adjusts the time by small fractions of a second. This way, the system time changes gradually, which avoids situations where file modification or creation time is in the future.