I have a samba share running on my server (just an Intel N100 Mini PC). It’s running Fedora Atomic and my desktop is also running Fedora Atomic.
While it’s good enough to watch videos on, reliability when it comes to uploading files to it has been very poor. The connection ends up timing out after a few minutes of uploading.
I found that using rsync to upload files to it has been a lot more reliable.
You must log in or # to comment.
No problems with it here, I’ve uploaded a W10(5.7GB) iso and 30GB worth of Music without an issues. The host computer is running DietPi which is Debian based.
Since there is no M$ machine in my network I removed samba and simply just use sftp everywhere.
You might want to check
sshfsbut overall yesrsyncworks well. I just uploaded 200Go yesterday, no failure.On my LAN if I want to share without downloading them then I rely on MiniDLNA/ReadyMedia for DLNA/UPnP meaning it works with
VLCon desktop, obviously, Android video projectors, mobiles, etc.Guess it depends on your usage but I stopped using Samba when I didn’t have Windows machines on my network. Never looked back.
In debian/ubuntu I just use the file browser and connect via sftp or whatever. I save the password and put the location in my sidebar for easy access. It works great for playing videos and other uses, although might want to setup jellyfin or similar for videos.
Pain and suffering
Smbfs by autofs for decades. 0 issues.
They’ve worked fine for me, unless the issue of file permissions starts to rear its ugly head.
Maybe watch your system logs on the server when it’s having trouble, could be something random.
If you dont care about permissions, use NFS. If you need protected shares, use SMBv3, force blocking of SMBv1 protocol.
I have a mix of both NFS and SMBv3 shares between NAS, Windows 11, Ubuntu, and MacOS machines. It can be done, not too difficult unless you are trying to mount things weird in proxmox or something.
Could be this https://omnitech.net/reference/2023/03/15/0x8007003b-timeout-copying-large-file-to-samba-server/
Or could be if you copy it via Nautilus GUI, people have suggests doing a straight cp from CLI has better results than Nautilus.
I have the same issue with sftp and webdav. (20GB zip file)
Maybe a buffer issue, does scp work?
Unusable for me on Fedora. I’m unable to watch movies or videos over network from NAS, have to copy it first
I’ve never had any issue with file transfers apart from being a bit slower than NFS. The main issues I have with it is lack of Unix file permissions and not allowing all characters in file names.
Unless you need compatibility with windows, you are better off using NFS or SSHFS.
NFS lacks security unless it’s NFSv4 paired with Kerberos AFAIK.
If it’s both *nix, why not NFS? Even Win10 with UTF-8 works well with my NFS server. These days my SMB server is only for Win7 and Android.
If you force turn off SMBv1, should work with win10/11
I have a mix of nfs and smbv3 shares with linux, mac, windows machines. Use nfs for video/music sharing for all. SMBv3 for protected private files.
Edit: i read your comment wrong.
It’s running Fedora Atomic and my desktop is also running Fedora Atomic.
Then why are you using Samba? It’s primarily for Windows. Use nfs or sshfs. Or if you’re running a media server, you could run an additional file management service like filebrowser.
No issues using SMB with my Unraid and transferring to/from my main Fedora 42 KDE PC.
