Yanked power to macmini.lan after the rsync completed, then turned it on again
marcan@raider:~/tmp -$ ls file.txt
ls: cannot access 'file.txt': No such file or directory
marcan@raider:~/tmp 2$ ssh macmini.lan
Last login: Thu Feb 17 23:45:26 2022 from 192.168.3.10
marcan@Mini-M1-2020 ~ % ls file.txt
ls: file.txt: No such file or directory
At least I’m not as rude as you. You’ll need to be persistent to accomplish your results with the Asahi Linux project - good luck with that.
I had no doubts that you can lose your file if you are moving it and some very lucky power outage hits. I was not “pretending” it's not real.
What I have doubts about, is that it's a real concern for 99.93% of the users. As we’ve found here, it's not even a rare case in other kinds of OS, so users would definitely notice it.
It is theoretically possible, of course. In practice, it's just too rare to consider.
But still, I hope this topic will be noticed by Apple and they fix that low performance issue for fullsync. Also, I hope they will not make fullsync as the default behavior - it doesn't worth the risks (and those for whom it does - should use some Linux for sure).
You're missing the point. Anything wanting data integrity will now have to use F_FULLFSYNC, which is slow on this firmware. You might say "you shouldn't care about data integrity to this degree", but databases do, and lots of developers run databases on their machines, and now they'll be real slow. Maybe they'll add some config options like `i_promise_i_dont_care_about_data_integrity = 1`, but come on.
This is real, please stop pretending it isn't.