Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The migration from HFS to APFS does not move your files at all. It leaves the files exactly where they are on the disk. Instead of moving the files, it writes new the new APFS metadata onto unused areas of your disk. When it's done with that, it changes the superblock header to point to the new APFS metadata. Then it marks the old HFS metadata as blank space. Your files are not moved or copied.

By doing it this way, they make the dangerous part of the process as small as possible. They actually did a dry-run to collect success/failure metrics before APFS was released to iOS devices:

https://www.macobserver.com/analysis/apple-dry-run-apfs-prio...



> Your files are not moved or copied.

:extremely pedantic voice: ITYM your data is not moved. Your inodes are.

:normal voice: thank you for taking the time to explain clearly this in more detail.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: