Looks like you’re hitting a TimeMachine SMB Bug when setting the Time Machine Max Size parameter in the admin UI. Please set the Max Size for TM Backups to default. You may need to take a new backup or use AFP to workaround the issue.
[2021/02/25 20:29:25.213791, 0] …/source3/smbd/service.c:885(make_connection_snum)
CIFS: [ipv4:192.168.1.27:54000] connected to [TimeMachineBackup] as user [nobody].
[2021/02/25 20:29:25.233686, 0] …/lib/util/charset/codepoints.c:16656(get_conv_handle)
dos charset ‘CP850’ unavailable - using ASCII
[2021/02/25 20:29:25.300195, 0] …/source3/modules/vfs_fruit.c:6995(fruit_tmsize_do_dirent)
fruit_tmsize_do_dirent: tmsize overflow: bandsize [134217728] nbands [1026]
[2021/02/25 20:29:25.300267, 0] …/source3/smbd/dfree.c:307(sys_disk_free)
sys_disk_free: VFS disk_free failed. Error was : Success
Well well well
Not quite.
Updated to v5.12.108.
Set a TimeMachine limit to 2TB (26%)
Error is back (see picture below).
I will try to download the logs (they are not coming right now, after restarting the NAS). @WDStaff let me know if you need them. (I managed to download them with Firefox, Safari would not do it on macOS Big Sur for some reasons…)
Apparently, the size limit I set (20%), despite being significantly beyond the current use of the TM share was not enough. With his help, I tried with a 95% limit and it worked. I am now running with a 30% limit and it still works (with at least one of the three computers).
June 22nd UPDATE
It stopped working. I guess it reached some sort of size limit (although there is plenty of room if you compare the current size of the the backups and the size limit set) and instead of erasing older backups (if needed) it simply stopped working.
Only SMB2 and SMB3 are enabled, but TmeMachine Backups are only working with no space limitation on the share. As soon as I set it to anything lower than a 100% the issue with not finding the share returns.
I tried turning backups off and on, deleting and adding the disk in Time Machine preferences, setting up Time Machine using the admin account or as Guest - it does not matter. I tried creating a separate user and using its share, making the backup share private or public - nothing matters and the error always comes back.
on one version of mac os beta i did a fix alias command to my link to the nas and then did not get the error. As that got TM working I did not do more testing.
I’ve had the same problem and tried turning the “Drive Sleep” option off in settings. So far, the bundle can still be accessed without a reboot. Uptime as of now is roughly 48 hours.