4 ms·
> "we were trial migrating your whole file system … consistency checking it … reporting back to us whether the upgrade was 100 percent clean, then rolling it ba
by dwattttt 3y ago
> "we were trial migrating your whole file system … consistency checking it … reporting back to us whether the upgrade was 100 percent clean, then rolling it back"
Actually doing the migration then undoing it is very much not a dry run. I assume they included an "if anything goes wrong, restore everything from iCloud" check or something, because otherwise an unexpected flaw in migration/rollback could mean data loss.
- DigitalHackOp 3y agoOne key feature of APFS was the metadata location didn't overlap with any hfs+ metadata location, so the two file systems could co-exist on the drive. So I presume they created the apfs metadata inside the hfs+ unallocated space, and so if it failed, hfs+ would happily overwrite the apfs metadata and continue on without any impact.
- nier 3y agoFrom the linked article: «Namely, in iOS 10.1 and 102 (sic!), metadata for APFS was test written and the superblock header was created but not actually written out. The file data remained untouched for safety and crash protection and the user remained in HFS+.»