That's interesting. I haven't tried connecting a CFast card to my Mac yet but if OSX is treating it like a drive instead of a card then that might explain why it's being written to and hence why some files are occasionally being corrupted. If you've ever connected a drive that's been connected to a Mac to a Windows machine, you'll see a load of hidden OSX files to do with Spotlight indexing and the trash.
That's an excellent observation, and could point to some issue with the CFast cards (the flash or controller).
You can only write data in chunks of the size of a flash block, which means that when a computer (or camera) writes really small files the card will be internally doing a read-modify-write operation (i.e. internally building a new flash block with your changes somewhere in the middle, then writing that block back out). As far as I'm aware, the controllers will favour writing that back to a new block, and marking the old block to be erased for reuse. I.e. even small operations on the card will be affecting more than just the tiny write that's being done. Any bug in the card controller's firmware, or potentially dodgy issue with the underlying flash, could well see files getting corrupted.
It would also explain why some people have initially loaded a "good" file from the card, but then later found it corrupted (assuming they hadn't actually just seen the embedded thumbnail the first time round and the raw data was actually corrupted all along).
I don't know if it's possible to mount the card read-only on Mac/Windows? On Linux I'm pretty certain it can be done, and that might reduce the chance of corrupting files when connecting a card to a PC.







and feather detail is nowhere near where I want.


