Hello,
when i tried to run a backup for a PVE Container it failed for the following reason:
which is a bit annoying after it ran 3 hours
Time stamps are in UTC.
According to log files the upload happened at 2020-07-10 11:54:11, and i know that the files got rsynced from ext4 filesystem to a zfs one around about 2020-07-18 09:50.
Modification dates are user settable, and the software doesn't really care if time is far in the past (it really shouldn't).
I "fixed" the time stamp for now, but i think you should rethink that "negative" time handling. Quite a few linux tools work correctly with negative time stamps (stat, ls, touch...).
Regards, Uwe
when i tried to run a backup for a PVE Container it failed for the following reason:
INFO: Error: error at "var/www/XYZ/data/upload/1732379/IMG_20200710_135246.jpg": file with negative mtimewhich is a bit annoying after it ran 3 hours
Code:
File: IMG_20200710_135246.jpg
Size: 1987555 Blocks: 3891 IO Block: 131072 regular file
Device: 80h/128d Inode: 3633376 Links: 1
Access: (0664/-rw-rw-r--) Uid: ( 3000/ XYZ) Gid: ( 3005/www-data)
Access: 2020-07-20 19:57:47.464799409 +0000
Modify: 1901-12-13 20:45:52.000000000 +0000
Change: 2020-07-18 09:50:27.283729176 +0000
Birth: -According to log files the upload happened at 2020-07-10 11:54:11, and i know that the files got rsynced from ext4 filesystem to a zfs one around about 2020-07-18 09:50.
Modification dates are user settable, and the software doesn't really care if time is far in the past (it really shouldn't).
I "fixed" the time stamp for now, but i think you should rethink that "negative" time handling. Quite a few linux tools work correctly with negative time stamps (stat, ls, touch...).
Regards, Uwe
