Click to See Complete Forum and Search --> : Samba buffers


int13
03-31-2005, 01:59 AM
Hi guys,

I have problems configuring Samba (Fedora Core 3).
The send/receive performance is very poor. I use these socket options:

socket options = SO_KEEPALIVE SO_REUSEADDR SO_BROADCAST TCP_NODELAY IPTOS_LOWDELAY IPTOS_THROUGHPUT SO_SNDBUF=8192 SO_RCVBUF=8192 SO_SNDLOWAT=0 SO_RCVLOWAT=0

when I mount remote smbfs it gives me an error , something like "SO_SNDLOWAT=0 unsupported protocol " or somethnig.

And also when I watch DivX over the LAN it freezes for a second at each 10 sec. it's probably caused from the buffer size.I tried to change it to 1024- the copy send performance over the smbfs improves but the film freezeng remains. I don't have this problem when I switch to Windows XP. The copying is ok and the DivX watching too.

Please give an advice. Thanks.

int13
04-01-2005, 05:11 AM
come on guys, anybody to help?

acid45
04-01-2005, 06:10 AM
i don't know samba can't help. I am trying to see if I can find something with what is here.

I found this, it was about very slow reading and writing speeds.

http://lists.samba.org/archive/samba/1999-December/016059.html


A quibble: IPTOS_LOWDELAY IPTOS_THROUGHPUT are opposites,
so only one will be used. I recommend IPTOS_LOWDELAY, but
don't expect this to have any measurable effect in your case...


I think that should answer your question, and I though I knew nothing about samba...


come on guys, anybody to help?

Never helps.

Hayl
04-01-2005, 08:54 AM
what version of samba (server side are you using) and what file system are you using to mount it client-side (CIFS or SMB)?

int13
04-01-2005, 08:59 AM
I can't tell you now what is the Samba version, but it's from Fedora Core 3 CDs. in my fstab I use :

//192.168.1.2/DATA /media/DATA smbfs uid=500,gid=500,umask=000 0 0


does this help?

Hayl
04-01-2005, 09:07 AM
Originally posted by int13
I can't tell you now what is the Samba version, but it's from Fedora Core 3 CDs. in my fstab I use :

//192.168.1.2/DATA /media/DATA smbfs uid=500,gid=500,umask=000 0 0


does this help?

not really... lol

Anyway, if it is a >= 3.X of SAMBA on the server (it probably is) then I highly recommend switching to CIFS instead of SAMBA in the kernel. There are known problems with new versions of SAMBA software and the SAMBA filesystem module that is in new(ish) Linux kernels. For example, I had issues with I/O when overwriting files when I was using the SAMBA filesystem module from the Linux kernel and then found out about the problems with it (SAMBA server <--> SAMBA kernel module client). After I switched to CIFS it worked properly. CIFS is based on the newer SMB protocol that the newer versions of Windows use other than that it behaves exactly the same as SAMBA.

You may not even need to redo your kernel. Try to modprobe cifs and see if they give it to you by default with Fedora. If they don't then recompile your kernel with it in and then change your /etc/fstab from smbfs to cifs.

Good luck.