does it happens to anyone ?

Num7

Num7

Administrator
Staff
Messages
12,509
Looks like a timestamp error. Glitches do happen in file systems. Nothing weird about it.

If that happens to you often, you might wanna check the integrity of your file system with a checkdisk. And never forget to backup your data.
 

I

Iamnoone

Junior Member
Messages
27
other files were from 44 and 2027 there are a lot of similar glitches in my life :)
 

Gacut

Gacut

Time wanderer
Messages
87
Sadly, this is only an error due to time implementation.

This date and time: 0:00, 1 January 1970 is called "Unix time".

Long story short, every single clock in computers are calibrated from this date and time.
Some programmer made a bug or just an easter-egg ;]

More about unix time: Unix time - Wikipedia
 
Harte

Harte

Senior Member
Messages
4,562
Gacut said:
Sadly, this is only an error due to time implementation.

This date and time: 0:00, 1 January 1970 is called "Unix time".

Long story short, every single clock in computers are calibrated from this date and time.
Some programmer made a bug or just an easter-egg ;]

More about unix time: Unix time - Wikipedia
Click to expand...
From your link:
On systems where Unix time is stored as a signed 32-bit integer, the largest value that can be recorded is 2147483647 (231 − 1), which is 03:14:07 Tuesday, 19 January 2038 UTC. The following second, the clock will wrap around to negative 2147483648 (−231), which is 20:45:52 Friday, 13 December 1901 UTC. This is referred to as the Year 2038 problem.
Click to expand...
Uh oh!
Airplanes will fall from the sky as the world ends due to the Y2K+38 bug!

Harte
 

Top