Apple is the only company that makes such terrible file systems. I have resized partitions on NTFS and EXT3 and never lost any data. Apple is uniquely terrible in terms of file systems and data integrity in general.

It just never works. And just when you think it's finally reliable and has worked for a while, it breaks in new unexpected ways. Sometimes hanging the whole machine. This was with both macOS as a server and a Linux server (less issues with Linux, but still broken).

Samba isn't great on other OSs either, but not as broken as on macOS. At this point I've given up on Samba completely, and consider it something I won't use again.

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.

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.

Carbon Copy Cloner was excellent at creating a bootable backup, and Super Duper seemed very serviceable too.

If/where there's hotfixes or patches needed, seeking scripts that can run when waking seem to be the only way to ensure any connectivity remains in place when opening one's laptop.

Maybe your distro’s samba is out of date?

I don't compile off of a Samba share for example, or do operations involving tons of small files frequently.

I'd use SMB only if I had to connect to some corporate server on Windows, or if whetever system I connected to didn't support anything else.

But a few weeks before release, Sun was acquired by Oracle.

It was going to take months of further negotiations to nail it down. Apple-sourced ZFS on macOS was canceled.

ZFS had been released by Sun before the Oracle Situation under their MIT-like CDDL.

I suppose when Big Tech is involved, they rattle patents at one another until the dust settles with handshakes and payouts all around. I'm speculating here. But I was told that the CDDL was not considered sufficient for Apple to support its own development efforts.

ZFS is relatively complicated, but it generally works. At the time, Apple was shipping servers with iSCSI SAN and a GUI comparable to Disk Utility.

Really a shame. I was running native ZFS on my Mac Pro that summer. Eventually migrated those pools to Open Solaris and eventually to Linux.

It can feel like until there's a bit more clarity or certainty publicly, or personally running multiple backups on different file systems is the default start, which isn't always ideal.

I like storage to become, and remain an appliance.

It doesn’t really have a stable and battle tested competitor in the FOSS arena considering its feature set.

(Of course there are things like Lustre and Glustre, but these are orthogonal solutions for different use cases.)

For workstations I just use the distribution default. APFS on Mac, NTFS windows, and my Linux distro happens to use btrfs by default.

No widely-deployed filesystem before or since ZFS is in the same league.