I have a volume in Windows Server 2016 that is a target of the data deduplication role.
It works very well ~60% savings rate, with many files appearing as zero bytes on the disk.
The volume is shared over SMB and mounts fine on Mac, Windows and Linux clients. The latter two can use all files as normal, but the Macs can't.
On any file that appears as using zero disk space the Macs don't know how to read them. They can't be opened or read, and a copy in Finder produces Error code -36
.
On a working client, copying the file to a new one so that it hasn't been deduplicated yet allows the Mac to read it, since it now appears to use disk space. For example, doing the following on Ubuntu will get the file to lose optimization: cp original_file.csv temp && mv temp original_file.csv
Is this a problem that can be solved, or is there something wrong with macOS or the way it implements SMB?