A piano #timemachine !
#TimeMachine on #macOS 26.5 still failed trying to back up to my Samba server.
The fix was to remove
fruit:time machine max size=…
from the share's smb configuration. As an alternative one can use tmutil to enforce a quota:
tmutil destinationinfo
sudo tmutil setquota [destination uuid] [quota-in-gb]
How to make and roll back to a snapshot
https://fed.brid.gy/r/https://eclecticlight.co/2026/05/07/how-to-make-and-roll-back-to-a-snapshot/
ok maybe I'm hitting this Samba bug in Tahoe: https://www.reddit.com/r/MacOS/comments/1s2pfwi/if_264_breaks_time_machine/
Does anyone use a Mac Mini as a Time Capsule with access restricted to specific users?
I'm trying to replace my Time Capsule since Apple is phasing out the Apple Filing Protocol, and I can get things working with my Mac Mini as fileserver if I leave the backup directory open to Guest users.
But I'd prefer a little more security on my local network, so I try to limit access to specific user accounts. When I do that, I get the attached error message, even though I have zero problems connecting to the network drive in Finder using the same credentials.
Is user-limited access simply not an option?
I've had zero luck finding more-detailed error messages on client or server, and searching the web so far has yielded nothing useful.
Since #Gemini totally borked the code I thought I'd restore from backup to get most of the code working again and to use #ChatGPT to see if it could solve the problem that Gemini destroyed the code trying to solve.
I had #Apple's #TimeMachine show me the backups but the only ones it claimed to have for that file were minutes ago and 3 days ago, which was a lie. I had to drill into the TM backup disk myself to retrieve the file. Apple software quality is total 💩.