Serious Bug with sparseimage

Hello,
with 10.8 I created an 1TB self growing sparseimage. Then i moved the sparseimage to my NAS, a SMB share.
I often mounted the sparseimage from 10.8 and put new files in and unmounted it. Everything worked fine.

Now with 10.9 I can mount the sparseimage and also copy new files onto it, it also changes the "last changed" date and size. But after an unmount and an remount the new files are gone. and also the size is the size before i moved the new files to the sparseimage.

This bug always accurs, and also with an sparseimage created with 10.9.

But: It only appears when the sparseimage is on my NAS. I can perfectly write other files to the SMB share and they stay there, but not if I copy them to the sparseimage.

Very strange so don't make your backup that way, you may loose your data.

Ok Bug submitted.

I think it is not filesystem related, because the sparseimage is on an SMB share. I can also perfectly write to the share, but not in the sparseimage on the share. It looks as if the files were copied to the sparseimage, size, dates everything changes and looks fine. But there is no network traffic to the SMB server.

So when I copy a file to the mounted sparseimage, the file is not actually transfered to the NAS where the sparseimage is stored at. And after unmounting and remounting the sparseimage looks as nothing ever happened.

But only if the sparseimage is on my NAS, when it is on my desktop or so, then it works fine. Unter 10.8 it also worked fine with the NAS.

May be. It would be nice if someone could reproduce this behavior. Your just need an Windows Computer with an SMB share - an virtual PC would be sufficient.

And then create an growing sparseimage with diskutil, move the .sparseimage to the smb share, mount it, copy files to the image, unmount and remount and files are gone.

News:
.sparsebundle is not affected, it works as it should! But: .dmg has the same strange behavior as .sparseimage

Thank you!

The blog post is about sparsebundle which is not affected by the bug.

Hello, Apple believes that this Bug is fixed in OS 10.10 Yosemite. I cannot test it so ... can you confirm this statement from Apple?

Thank you!