2 ms·

I haven’t had that level of issues with CIFS on Apple platforms in general. For most of iOS 18 there was a bug where iOS and iPadOS simply couldn’t connect to

I haven’t had that level of issues with CIFS on Apple platforms in general. For most of iOS 18 there was a bug where iOS and iPadOS simply couldn’t connect to Samba shares on Linux but that has since been resolved. Apple does implement some custom functions that make CIFS (Samba or Windows based) shares less performant than Apple platform served shares in certain situations. Especially for server side copy. TrueNAS has recently patched this so that it works. Adopting/inheriting a CIFS-backed Time Machine share is needlessly precarious.

jval43 1y ago
> For most of iOS 18 there was a bug where iOS and iPadOS simply couldn’t connect to Samba shares on Linux but that has since been resolved. Yes, exactly. That bug also affected macOS Sequoia but IIRC could be worked around (not on iOS though). And that was just the latest series of bugs, the pattern repeats itself every once in a while and it got worse after they discontinued Mac OS X Server and their own Time Capsule. Every few months something breaks. E.g. just in March 2025, the 13.7.5 update to Ventura (last OS supporting a 2017 Mac) broke SMB filesharing for many users. There was a workaround, but it was only fully fixed in 13.7.7 four months later. The fruit extensions are useful for performance, but don't really help with connection issues / hangs. Aside from that, the main usecase they enabled in the past was working Timemachine backups, but my long-term experiences with Timemachine over the network (with Mac OS X Server, fully supported by Apple at the time) were less than stellar and so I'm not doing that ever again either. Overall, it's just not a level of reliability I'm comfortable with for a network filesystem implementation.