All Posts by Date or last 15, 30, 90 or 180 days.
also by Lloyd: diglloyd.com photography and WindInMyFace.com
Thank you for purchasing through links and ads on this site.
OWC / MacSales.com...
diglloyd Deal Finder...
Buy other stuff at Amazon.com...
Get up to 16x more storage and 2x the speeds of the original drive
Handpicked deals...
$2998 $2498
SAVE $500

$1199 $920
SAVE $279

$1999 $1599
SAVE $400

$2799 $2399
SAVE $400

$400 $280
SAVE $120

$1798 $1598
SAVE $200

$3297 $2797
SAVE $500

$3397 $2797
SAVE $600

$1398 $898
SAVE $500

$3698 $2998
SAVE $700

$1799 $1329
SAVE $470

$1999 $1199
SAVE $800

$2249 $1549
SAVE $700

$2399 $2049
SAVE $350

$2799 $1899
SAVE $900

$997 $897
SAVE $100

$2099 $1699
SAVE $400

$1999 $1369
SAVE $630

$1349 $949
SAVE $400

$4499 $3999
SAVE $500

$1499 $1029
SAVE $470

$1499 $1289
SAVE $210

$2199 $1999
SAVE $200

$3399 $2199
SAVE $1200

$2418 $1718
SAVE $700

OWC Thunderbolt 3 Dock
Ideal for any Mac with Thunderbolt 3


Dual Thunderbolt 3 ports
USB 3 • USB-C
Gigabit Ethernet
5K and 4K display support plus Mini Display Port
Analog sound in/out and Optical sound out

Works on any Mac with Thunderbolt 3

Copying Files in macOS Can Truncate File Date/Time to One-Second Granularity

A user of IntegrityChecker reported that verification of backups was resulting in claims of changed file dates. Investigating, I found that copying files from an APFS file system to macOS Extended changes the file dates by truncating the time to the second (truncating, not rounding).

Since macOS Extended supports file times to the millisecond, there is no good explanation for this behavior other than yet one more macOS bug.

It’s a hassle to have files reported with changed dates when verifying data, so I’m making a few changes to IntegrityChecker java version (icj) to handle this situation better, such as not flagging a date change if the new date has a zero millisecond component.

Example of whacked file dates

I used the dgl finfo command to print out this information. It uses 'Carbon' APIs.

This example from one file for brevity; it happens for all files I tested (thousands).

Original on APFS volume

DataFork:         53529, 57344, closed
CreationDate      2019-05-20 22:19:19.80359873 0.3641260759.57184
ContentModDate    2019-05-20 22:19:19.80359877 0.3641260759.57444

Copy on another APFS volume

DataFork:         53529, 57344, closed
CreationDate      2019-05-20 22:19:19.80359873 0.3641260759.57184
ContentModDate    2019-05-20 22:19:19.80359877 0.3641260759.57444

Copy on macOS Extended volume

DataFork:         53529, 57344, closed
CreationDate      2019-05-20 22:19:19.80359000 0.3641260759.0  <== millis truncated
ContentModDate    2019-05-20 22:19:19.80359000 0.3641260759.0

Simon N writes:

Are you sure HFS+ supports milliseconds? As far as I know, the date resolution on HFS+ is 1s, so it seems to be inevitable that the milliseconds from APFS-originating files get cut off. One might argue Apple could have implemented rounding instead of truncating, but the outcome would (essentially) be the same.

MPG: I see that Wikipedia shows "Date resolution" as "1s", so perhaps my assumptions are invalid.

Because macOS Extended (HFS Plus) uses a 48 bit number for date/time (16 bit each for High/Low/Fraction), I had assumed that non-zero values in the fraction part of the number were milliseconds.

Since many files have non-zero values in the fraction part, it only made sense that this represents milliseconds. But if the file system only does time to the second, then these values are essentially garbage, or being used for oddball purposes by Apple.


Save the tax, we pay you back, instantly!
View all handpicked deals...

Sony Alpha a7R III Mirrorless Digital Camera Body with Accessories Kit
$2998 $2498
SAVE $500

diglloyd.com | Terms of Use | PRIVACY POLICY
Contact | About Lloyd Chambers | Consulting | Photo Tours
Mailing Lists | RSS Feeds | Twitter
Copyright © 2019 diglloyd Inc, all rights reserved.
Display info: __RETINA_INFO_STATUS__