Hello!
When we were working with Linux, we had Linux/Windows workstations for every user and a shared Linux server. All files (projects, photos, music, etc.) of all users were stored on the Linux server and mounted via SMB, because backups are made only on the server. Now we have switched every Linux client to FreeBSD and, sorry, but the implemented SMB client is just unusable for today's work load. Everyone is complaining and I don't know what to do to fix that issue.
Here are my diagnostics:
1. The kernel module client ist really really really old and also seems to be no longer maintained.
2. The source does not include any caching at all. Every read request is directly sent to the server and the reply is then sent to the local pid on the client. This means that if a stupid program is reading in 1kb-chunks, the transfer speed goes down to a few 100kb/sec.
Practical example: If you are browing a photo folder with geeqie, it creates one thumb every 3 seconds. On a Linux box it creates 30 thumbs per second. Users just don't accept that.
I have tried the fusefs smb package, but that piece of software is the worst thing I have ever seen. Its equally slow, but its restricted to a single mount and it likes crashing.
Since I am not having the knowledge to code a new kernel module, I am searching for work arounds. So what can I do?
1. Is there something else to use than Samba? The folders need to be shared, so iSCSI isnt useable. NFS does not seem to be very secure to me.
2. If nothing else, how can I implement a read-ahead + caching layer? The SMB client has to use the max. block size and since by doing that it will read more than requested, it must implement a caching layer as well. Any ideas?
PS: Anyone feel free to create a replacement SMB client kernel module!
When we were working with Linux, we had Linux/Windows workstations for every user and a shared Linux server. All files (projects, photos, music, etc.) of all users were stored on the Linux server and mounted via SMB, because backups are made only on the server. Now we have switched every Linux client to FreeBSD and, sorry, but the implemented SMB client is just unusable for today's work load. Everyone is complaining and I don't know what to do to fix that issue.
Here are my diagnostics:
1. The kernel module client ist really really really old and also seems to be no longer maintained.
2. The source does not include any caching at all. Every read request is directly sent to the server and the reply is then sent to the local pid on the client. This means that if a stupid program is reading in 1kb-chunks, the transfer speed goes down to a few 100kb/sec.
Practical example: If you are browing a photo folder with geeqie, it creates one thumb every 3 seconds. On a Linux box it creates 30 thumbs per second. Users just don't accept that.
I have tried the fusefs smb package, but that piece of software is the worst thing I have ever seen. Its equally slow, but its restricted to a single mount and it likes crashing.
Since I am not having the knowledge to code a new kernel module, I am searching for work arounds. So what can I do?
1. Is there something else to use than Samba? The folders need to be shared, so iSCSI isnt useable. NFS does not seem to be very secure to me.
2. If nothing else, how can I implement a read-ahead + caching layer? The SMB client has to use the max. block size and since by doing that it will read more than requested, it must implement a caching layer as well. Any ideas?
PS: Anyone feel free to create a replacement SMB client kernel module!
