[HN Gopher] Apple Did a Dry Run of APFS on Your Device Even Befo...
___________________________________________________________________
Apple Did a Dry Run of APFS on Your Device Even Before iOS 10.3
(2017)
Author : tosh
Score : 42 points
Date : 2024-04-15 20:51 UTC (2 hours ago)
(HTM) web link (www.macobserver.com)
(TXT) w3m dump (www.macobserver.com)
| cptskippy wrote:
| Something something Microsoft spyware...
| samatman wrote:
| Good.
|
| If they're going to migrate my data to an entirely new file
| system, I want that tested as thoroughly as possible. This
| happened during the update, when you can't use the phone by
| definition, and was removed completely before the update
| finished. Who cares, it's running the middle of the night.
|
| Well, I care. I'm glad they did it, the migration went off
| without a hitch when they shipped it, I doubt I was even aware it
| had happened right away.
| dwattttt wrote:
| > "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 wrote:
| One 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.
___________________________________________________________________
(page generated 2024-04-15 23:02 UTC)