Hacker News new | ask | show | jobs
by tgma 562 days ago
Apple did something like this with a billion live OS X/iOS deployments (HFS+ -> APFS). It can be done methodically at scale as other commenters point out, but obviously needs care).
2 comments

You don’t need to look that far. Many of us here lived through the introduction of NTFS and did live migrations from FAT32 to NTFS in the days of Windows 2000 and Windows XP.

I still remember the syntax: convert C: /fs:ntfs

Yea thanks for recalling this. I totally forgot about that because I never trusted Windows upgrade, let alone filesystem conversion. Always backup and clean install. It's Microsoft software after all.
IIRC there was a similar conversion tool in Windows 98 for FAT16 -> FAT32.
When this first showed up I took 3 backups: two on networked drives and one on an external drive which was then disconnected from the system.

The second time I just went “meh” and let it run.

Craig Federighi on some podcast once said they conducted dry-runs of the process in previous iOS updates (presumably building the new APFS filesystem metadata in a file without promoting it to the superblock) and checking its integrity and submitting telemetry data to ensure success.
You can do all the testing in the world, but clicking deploy on that update must have been nerve wracking.
Apple doesn’t just deploy to the whole world in an instant though.

First it goes to the private beta users, then the public beta users, and then it slowly rolls out globally. Presumably they could slow down the roll out even more for a risky change to monitor it.

Sure, but still whoever wrote the patch had his ass on the line even shipping to a batch of beta users. Remember this is Apple not Google where the dude likely got promoted and left the team right after pressing click :)
Very much worth saying that many of the people what write code at Apple are women. Some of them are my friends.