A couple of days ago I upgraded the Samba package on my FreeBSD NAS from 4.19 to 4.20. I didn't test access to shares right away, but today I noticed that scheduled backups of my Fedora laptop to one of the Samba shares had failed.
It appeared that the share had mounted OK, the directory where the backups were saved was accessible, and all previous backup files were visible in there. However the backup utility logs were showing a "No such file or directory" when trying to open the manifest file of last week's successful backup, but it was plainly there and had correct permissions to access. I tried 'cat'ing the file in a bash shell and got the same error. 'stat'ing the file worked and 'getfacl' returned sane ACL entries.
I logged onto the FreeBSD NAS and was able to access the file just fine. There were no errors in /var/log/messages or any of the samba log files.
I booted my laptop into Windows 11 and tried accessing the file, but got an error about the file not existing (having just double-clicked it in File Explorer) and asking if I wanted to create it. Trying to access any other file on any other share also returned similar errors.
I downgraded Samba back to 4.19 and everything started working again.
It looks like the samba420 package has a problem and I'm going to file a report for it, but I wanted to check whether anyone else has encountered the same thing
It appeared that the share had mounted OK, the directory where the backups were saved was accessible, and all previous backup files were visible in there. However the backup utility logs were showing a "No such file or directory" when trying to open the manifest file of last week's successful backup, but it was plainly there and had correct permissions to access. I tried 'cat'ing the file in a bash shell and got the same error. 'stat'ing the file worked and 'getfacl' returned sane ACL entries.
I logged onto the FreeBSD NAS and was able to access the file just fine. There were no errors in /var/log/messages or any of the samba log files.
I booted my laptop into Windows 11 and tried accessing the file, but got an error about the file not existing (having just double-clicked it in File Explorer) and asking if I wanted to create it. Trying to access any other file on any other share also returned similar errors.
I downgraded Samba back to 4.19 and everything started working again.
It looks like the samba420 package has a problem and I'm going to file a report for it, but I wanted to check whether anyone else has encountered the same thing