Timeline for Mac OS X - exFAT file modification time issue
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2019 at 14:51 | comment | added | gollum |
And also nope regarding your assumption about linux exfat using local time. I've looked at the images's hex dump and it uses 0x00 for the timzone offsets. That means the linux exfat fuse driver stores the timestamps in UTC. However, +1 for making me check if the bug is time zone related, which seems to be the case.
|
|
| Jan 3, 2019 at 16:41 | vote | accept | gollum | ||
| Jan 4, 2019 at 13:41 | |||||
| Jan 3, 2019 at 16:38 | comment | added | gollum |
It really is timezone related but your assumption is wrong. I've analyzed the FAT table in my hex editor and no matter which timezone the system uses, my OSX always writes 0xFC for all three (create, modify, access) TimezoneOffset. These values are stored as signed bytes (0xFC is -4 in decimal) and interpreted as offset from UTC in 15 min increments. In other words El Capitan always uses a time zone offset of UTC-01:00 when writing exFAT time stamps.
|
|
| Jan 3, 2019 at 13:50 | comment | added | grawity_u1686 |
Example looks fine. You gave touch 03:00 local time, it was translated to something like 01:00 or 02:00 UTC when storing on disk. Then it was read back from disk by ls and translated back from UTC into 03:00 local time before displaying it.
|
|
| Jan 3, 2019 at 12:59 | comment | added | gollum | nope, look at the 3am example | |
| Jan 3, 2019 at 12:50 | history | answered | grawity_u1686 | CC BY-SA 4.0 |