APFS Bug in macOS High Sierra Can Cause Data Loss When Writing to Disk Images

[hemon]

What exactly are you trying to "fix"?

Your problem doesn't sound related to this one at all.

I lost free space on an APFS formatted hard drive – two times!

The first time I thought I had some hidden files, so I formatted everything.
The second time I had the same, and then no free space more at all. Suddenly, the hard drive did not worked anymore because of an error with the partition table, and so I had to format again – now as HFS+. The hard drive, which was new, works 100%.

 

[sdf]

I lost free space on an APFS formatted hard drive – two times!

So no, it's not the same bug.

 

[hemon]

So no, it's not the same bug.

Ok, then sorry for this.

Anyway, this is a very strange problem – which I never had before the APFS.

 

[chucker23n1]

I lost free space on an APFS formatted hard drive – two times!

The first time I thought I had some hidden files, so I formatted everything.
The second time I had the same, and then no free space more at all.

You're probably seeing purgeable storage.

Suddenly, the hard drive did not worked anymore because of an error with the partition table, and so I had to format again – now as HFS+. The hard drive, which was new, works 100%.

OK, that sounds bad, but unless this was in a sparse disk image, it has nothing to do at all with this thread.

 

[hemon]

You're probably seeing purgeable storage.



OK, that sounds bad, but unless this was in a sparse disk image, it has nothing to do at all with this thread.

Thank you for this reply.

Maybe you're right.

Anyway, I don't want to pass to APFS anymore for my hard drive.

I also read that this format should be for SSD drives and not for HD which would be better with the old HFS+.

 

[ehof]

My APFS formatted sparsebundle suddenly stopped opening. Disk utility will not fix the problem. MY sparsebundle is pretty big 7.8TB on an 8TB drive and I'm using OS10.13.3. Am I doomed or is there any script to fix or somhow force open it?

 

[name99]

My APFS formatted sparsebundle suddenly stopped opening. Disk utility will not fix the problem. MY sparsebundle is pretty big 7.8TB on an 8TB drive and I'm using OS10.13.3. Am I doomed or is there any script to fix or somhow force open it?

Most LIKELY problem is hardware failure, something like an file-system essential block went bad before it could be remapped.
You could try using something like DriveDX which may be able to tell you if there's an issue. You won't be guaranteed a diagnosis, but it may give you some insight.

 

[ehof]

Thank you. Not sure if this makes any difference. I forgot to mention that I tried to fix the sparsebundle with disk utility which thinks everything is okay. After doing so the error stopped but the image didn’t open. It’s only once I stated to play with the terminal that the error came up. My guess is that if I will try first aid again from disk Utility the error will stop appearing.

 

[CamNYC]

quote: The bug has already been fixed in Apple's upcoming iOS 11.3 and macOS 10.13.4 software updates.

I know this is an old thread, but I just found out about this specific bug now. Reading your comment close to the top, it seems your quote implies the bug of the title, in question has already been fixed. And yet it's a half quote about another totally unrelated bug, which gets mentioned with the explanation that, "in their defense", in *that* particular case Apple had already patched the bug.

But not *this* bug!

Did you even read the whole article? And if so, what was the purpose of your comment? To misguide readers? to defend Apple?

 

[chucker23n1]

I know this is an old thread, but I just found out about this specific bug now. Reading your comment close to the top, it seems your quote implies the bug of the title, in question has already been fixed.

Are you sure this bug still exists as of Big Sur?

(edit) Bombich says it was resolved in 10.14.