Comment by EugeneOZ
4 years ago
This means the world would be full of complaints from macOS users, but for some reason, we only know about this detail because of that “shocking” Twitter thread.
4 years ago
This means the world would be full of complaints from macOS users, but for some reason, we only know about this detail because of that “shocking” Twitter thread.
Run that on a Mac Mini. Do it a couple times. Remember the timestamp of the last one. Let it count down, then pull the plug within a few seconds after "done!" shows up. Boot up again. The file contents will have reverted to a prior point in time.
This isn't some hypothetical thing, this is a trivial test you can do. fsync() on macOS does not guarantee data is on stable storage. And this is actually well documented.
Then if you want to see the performance problem, make it a loop instead and use `fcntl.fcntl(fd, fcntl.F_FULLFSYNC, 1)`. You'll get 40-odd IOPS, but at least your data won't disappear after power loss.
Does it somehow prove that people are losing files when transferring them over the network? People would definitely notice it.
You're very persistent, aren't you?
Yanked power to macmini.lan after the rsync completed, then turned it on again
Data's gone.
This is real, please stop pretending it isn't.
6 replies →
Looking at the Apple support forums, the world is full of complaints about all sorts of malfunctions (which may or may not be related).
Not sure if intentional or not, but it was a good joke, thanks :)