DavRic

Recently upgraded my Unraid instance from 6.7.x to 6.12.2. Previously I used AFP for Time Machine backups and had to switch to SMB. In order for Time Machine on my Mac to see my Unraid share (configured as \\UNRAID\\TimeMachine) I had to add SMB extra options: fruit:time machine = yes fruit:time machine max size = 1T This worked completely fine. I then ran into a possibly related issue when trying to copy files from a Windows 10 PC to a different share (\\UNRAID\Games). Copying a file of any size from the Windows 10 PC to the share results in the same exact error (0x8007003B) from the attached thread. Creating files was somehow OK though? I began troubleshooting this problem and while watching syslog, I noticed any time I tried to a copy a file to \\UNRAID\Games, this error would occur: Jul 12 20:26:31 UNRAID smbd[13798]: [2023/07/12 20:26:31.418688, 0] ../../source3/smbd/dfree.c:132(sys_disk_free) Jul 12 20:26:31 UNRAID smbd[13798]: sys_disk_free: VFS disk_free failed. Error was : Not a directory The ONLY way I've found to get around this problem is to adjust the SMB share settings for any share I want to write to (\\UNRAID\Games). Export must be set as "Yes/Time Machine" which enables the option to set a size for the share. I then set the size to 1,048,576 (1TB). After these changes, the sys_disk_free errors go away and I am able to transfer files as expected. Not requesting follow up, just wanted to pass along this bug and potential root cause to hopefully improve Unraid. I don't anticipate this fixes all variations of the 0x8007003B error, but at least one kind.