Bug in macOS High Sierra APFS can cause data loss when writing to disk images

After so many steps in relation to Apple's operating systems this year, with loopholes, errors, etc., we cannot understand and appreciate the idea of ā€‹ā€‹wanting to abandon stratospheric annual updates to focus on security updates and have more time to improve its new features, making the most significant updates something biannual, probably.

It was funny that Eduardo Marques commented, in the on Air # 266, that Apple was able to migrate its systems to the Apple File System (APFS) so well, without any problems, and now, even this migration doesnā€™t seem to have really been done the way we expected from Ma.

The developer Mike Bombich published on his blog, last Thursday (15/2), a news that can affect users who migrated to the new Apple file system:

This week, we informed Apple of a serious flaw in macOS that can lead to data loss when using an APFS-formatted disk image. Until Apple issues a macOS update that resolves this issue, we are abandoning support for APFS-formatted disk images.

But before you despair, know that this problem does not affect normal APFS volumes, that is, SSD boot disks. The problem happened with sparse disk images (sparse disk images) on APFS, which simulate a physical drive mounted on your Mac and are normally used to back up or clone disks (which, for some, can be a big problem).

According to Bombich's account, the disk had two main problems: the first was that the drive created in sparse APFS did not update as data was being placed on it, always showing that the drive was empty. The other problem is the lack of error reports when recording requests fail to dynamically expand the disk image, which ends up ā€œwritingā€ the data in an empty space.

Below, you can see a Bombich video reproducing the bug:

You can read more details in the original post on the developer's blog.

With this bug, there is no possibility of ignoring that some changes do need to be made at Apple. And it's a good thing that apparently this has already started, at least.

via MacRumors