Re: Samba Problems - SLOW coppies to Windows Client

Dave Lewis wrote:
> I'm having a problem between windows vista and samba..

I've never tried to access a SAMBA share with Vista, but I'll see what I can
do.

> Server is a Quad PIII 700 with 8gig ram, full SCSI Raid and 1Gb connection
> Desktop is a Quad AMD 4 gig of ram SATA mirror and 1Gb connection.

Can hardware like that even handle a 1Gb connection?  I mean, sure, there
should be sufficient CPU to process the incoming traffic, but are the bus
speeds fast enough to do a full Gb?

> FTP Transfers and everything else seems ok but Samba is garbage..    
> Reading from a samba share to my desktop I get a MAX of 200KB/s.
>
> Copies from my 2003 server to the desktop are fine as well.
>
> ipref doesn't show anything major.

So, it's not a raw bandwidth issue.

Some random questions:

1) What's your network architecture like?  Everything on the same physical
and logical network?  Any routers, firewalls, bridges, etc. that might
introduce a second broadcast domain?  It looks like it's a contained /16,
but I'd like to make sure.

2) What's traffic like between 2003 Server and SAMBA?  Akin to traffic
between the Desktop and SAMBA?  Or more like traffic between the Desktop and
2003 Server?

3) Reads in the direction of SAMBA -> Desktop are slow; what about writes in
the direction of Desktop -> SAMBA?

4) If you strip out all the optimizations, options, etc., what do you see?

5) Have you tried to do a tcpdump on the SAMBA server while a read is in
progress, to see what the traffic actually looks like?

Some comments on your configuration file...

> [global]
>         read raw = yes                     # Default
>         write raw = yes                    # Default

It's possible your desktop is acting funny; try changing these to 'no' and
see if that helps.  Unlikely, but possible.

>         oplocks = yes                      # Default
>         max xmit = 65535                   # Default
>         dead time = 15                     # Default is 0
>         getwd cache = yes
>         lpq cache = 30
> [okplace]
>         veto oplock files = this/that/theotherfile
> [badplace]
>         oplocks = no
                                                                                                                                                                                   

I'm assuming the below all falls under [global], and not [badplace]...

> workgroup = LEWIS
> server string = Samba Server %v
> log file = /var/log/samba/log.%m
> max log size = 50
> log level = 5
> hosts allow = 127. 10.10. 192.168.1.
> map to guest = bad user
> security = user
> socket options = TCP_NODELAY IPTOS_NODELAY IPTOS_THROUGHPUT

Assuming everything's on the same network, IPTOS_THROUGHPUT is probably
extraneous here.  I'd consider adding those 64k buffers back in, though.

>    os level = 250

You know, I'd always thought that the *lower* the value, the higher the
priority.  Turns out I'm wrong.

>    preferred master = yes
>    dns proxy = no

Unrelated, but have you thought about a WINS server?  Since you're pushing
to be the master browser anyhow, WINS isn't going to hurt you at all, and
could possibly help a fair bit.

  - Damian
-- 
OCLUG general discussion list
[email protected]
http://oclug.on.ca/mailman/listinfo/oclug