ok, let's compare the ways rclone can access a smb/samba server.
- rclone's samba remote. as you noted, lacks many basic features, would not use.
rclone config smbserver:
[smbserver]
type = smb
host = XXX
user = XXX
pass = XXX
rclone copy file.ext smbserver:share -vv
DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "copy" "file.ext" "smbserver:share" "-vv"]
DEBUG : Creating backend with remote "file.ext"
DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
DEBUG : fs cache: adding new entry for parent of "file.ext", "/root"
DEBUG : Creating backend with remote "smbserver:share"
DEBUG : smb://username@server:445/share: Using root directory "share"
DEBUG : file.ext: Need to transfer - File not found at Destination
INFO : file.ext: Copied (new)
- mounting the smb/samba share. supports modtime, checksums,
--inplace, more...
mount.cifs -o user=username,pass=password //smbserver/share /mnt/share
rclone copy file.ext /mnt/share -vv
DEBUG : rclone: Version "v1.64.0" starting with parameters ["rclone" "copy" "file.ext" "/mnt/share" "-vv"]
DEBUG : Creating backend with remote "file.ext"
DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
DEBUG : fs cache: adding new entry for parent of "file.ext", "/root"
DEBUG : Creating backend with remote "/mnt/share"
DEBUG : file.ext: Need to transfer - File not found at Destination
DEBUG : file.ext: md5 = b026324c6904b2a9cb4b88d6d61c81d1 OK
DEBUG : file.ext.xibuvak3.partial: renamed to: file.ext
INFO : file.ext: Copied (new)