samba - Apr 2001 - Slow Copy WinXX - Linux/Samba :-(

I never thought it would happen to me, but it did...

I have read threads about slow copies from WinXX to Linux/Samba on the
list in the past, but I don't recall a concise answer regarding what the
cause was.

THE PROBLEM:

Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named
"Nemesis" - for good reason), the transfer speed slows to a crawl. The
Win95 copy dialog box starts out by saying 25 seconds remaining , then
60 seconds remaining, then 2 minutes, then 5 minutes, and so on.  I HAVE
NEVER HAD THIS PROBLEM IN THE PAST.

I have tried reboots of the Win95 box -- no joy. I have tried copying
smaller files to Nemesis (~200k) no noticable problem. I have tried
copying large files from "Nemesis" to Win95 (or Win98 or WinME)  and
it
screams (No Problem -- 1.5 meg so fast the copy dialog doesn't even have
time to appear). I need help, something is amiss, at best, and FUBAR at
worst.

When I set up my server, I copied all of my firm's data from the Win95
machine to "Nemesis" with no problem. Approximately 355 Meg copied in
~
20 sec. (don't quote me on this, but it was less than a minute - after
not having to reboot the Linux machine since 1/19, my memory fades -
stupid human falability)

MY SYSTEM:

Abit KT7/AMD 800 T-bird
256M Ram
IBM 45G/7200 RPM ATA/66 drive
Linux Mandrake 7.2 (stock ISO install)
Samba 2.07 (Same stock ISO install)

    REST OF NETWORK: Win95, Win98, WinME (5 total)

CHANGES SINCE STOCK MANDRAKE INSTALL:

Loaded PopTop pptpd server
Loaded xntp time sync program (xntp is not currently running)

MY SMB.CONF

#************************************************************
# Samba config file created using SWAT
# from localhost.localdomain (127.0.0.1)
# Date: 2001/01/19 00:04:36

# Global parameters
[global]
 workgroup = RB_LAW
 server string = RB_LAW Samba Server %v
 encrypt passwords = Yes
 update encrypted = Yes
 smb passwd file = /etc/smbpasswd
 passwd program = /usr/bin/passwd %u
 passwd chat = *New*password* %n\n *new*password* %n\n *success*
 passwd chat debug = Yes
 unix password sync = Yes
 log file = /var/log/samba/log.%m
 max log size = 50
 name resolve order = wins lmhosts hosts bcast
 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
 printcap name = lpstat
 logon script = %U.bat
 domain logons = Yes
        time server = yes
 os level = 34
 preferred master = Yes
 domain master = Yes
 dns proxy = No
 wins support = Yes
 hosts allow = 192.168.7. localhost
 min print space = 2000
 printing = cups
 print command = /usr/bin/lp -d%p -oraw %s; rm %s
 lpq command = /usr/bin/lpstat -o%p
 lprm command = /usr/bin/cancel %p-%j
 queuepause command = /usr/bin/disable %p
 queueresume command = /usr/bin/enable %p

[netlogon]
 comment = Rankin-Bertin logon services
 path = /home/samba/logon
 browseable = No

[Rankin-Bertin]
 comment = Rankin-Bertin PLLC
 path = /home/samba/rbpllc
 valid users = @rbpllc
 force group = rbpllc
 admin users = david
 writeable = Yes
        map archive = Yes
        inherit permissions = Yes

[homes]
 comment = Homes Directory
 writeable = Yes
 browseable = No

[config] # ** I know this aint smart but I use it daily -- so save the
keystrokes (comment added for post to list)
 comment = Admin Config Share
 path = /
 valid users = david
        force user = root
 force group = root
 admin users = david
 writeable = Yes

[Applications] # ** New share added 4/19 to hold WinXX application
programs (comment added for post to list)
 comment = Windows Applications
 path = /home/samba/winapps
 valid users = @rbpllc
 force group = rbpllc
 admin users = david
 writeable = Yes
        map archive = Yes
        inherit permissions = Yes

[printers]
 comment = The Printing Army
 path = /var/spool
 guest ok = Yes
 printable = Yes
 printer = lp
#************************************************************

CHANGES TO SMB.CONF SINCE INSTALL

Addition of [Applications] share (as shown above in the smb.conf)

QUESTION:

What in the world is causing the slow copy behavior from my WinXX box to
"Nemesis"? I don't get it! I can copy FROM Nemesis to WinXX
without any
problems -- I just can't do it in reverse. In the past I have sent 300+
Meg of data to the server with no problem. Now it stalls trying to copy
anything bigger than ~200k from Windoze to Linux. What should I check? I
don't think 'pptpd' or 'xntpd' should have anything to do
with smb
(xntpd isn't even running - pptpd is the only new process running).  (I
HAVEN'T REBOOTED MY LINUX MACHINE SINCE 1/19 - DO YOU THINK A REBOOT
MIGHT HELP?)

Anyway, for all of the others that have run into slow copy times from
WinXX to Linux/Samba, - Please let me know if you have found a FIX, or
WORK AROUND.

Thank You,

--
David Rankin
Nacogdoches, Texas

David Rankin wrote:
> 
> I never thought it would happen to me, but it did...
> 
> I have read threads about slow copies from WinXX to Linux/Samba on the
> list in the past, but I don't recall a concise answer regarding what
the
> cause was.
> 
> THE PROBLEM:
> 
> Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named
> "Nemesis" - for good reason), the transfer speed slows to a
crawl. The
> Win95 copy dialog box starts out by saying 25 seconds remaining , then
> 60 seconds remaining, then 2 minutes, then 5 minutes, and so on.  I HAVE
> NEVER HAD THIS PROBLEM IN THE PAST.
> 
> I have tried reboots of the Win95 box -- no joy. I have tried copying
> smaller files to Nemesis (~200k) no noticable problem. I have tried
> copying large files from "Nemesis" to Win95 (or Win98 or WinME) 
and it
> screams (No Problem -- 1.5 meg so fast the copy dialog doesn't even
have
> time to appear). I need help, something is amiss, at best, and FUBAR at
> worst.
> 
> When I set up my server, I copied all of my firm's data from the Win95
> machine to "Nemesis" with no problem. Approximately 355 Meg
copied in ~
> 20 sec. (don't quote me on this, but it was less than a minute - after
> not having to reboot the Linux machine since 1/19, my memory fades -
> stupid human falability)
> 
> MY SYSTEM:
> 
> Abit KT7/AMD 800 T-bird
> 256M Ram
> IBM 45G/7200 RPM ATA/66 drive
> Linux Mandrake 7.2 (stock ISO install)
> Samba 2.07 (Same stock ISO install)
> 
>     REST OF NETWORK: Win95, Win98, WinME (5 total)
> 
> CHANGES SINCE STOCK MANDRAKE INSTALL:
> 
> Loaded PopTop pptpd server
> Loaded xntp time sync program (xntp is not currently running)
> 
> 
> CHANGES TO SMB.CONF SINCE INSTALL
> 
> Addition of [Applications] share (as shown above in the smb.conf)
> 
> QUESTION:
> 
> What in the world is causing the slow copy behavior from my WinXX box to
> "Nemesis"? I don't get it! I can copy FROM Nemesis to WinXX
without any
> problems -- I just can't do it in reverse. In the past I have sent 300+
> Meg of data to the server with no problem. Now it stalls trying to copy
> anything bigger than ~200k from Windoze to Linux. What should I check? I
> don't think 'pptpd' or 'xntpd' should have anything to
do with smb
> (xntpd isn't even running - pptpd is the only new process running).  (I
> HAVEN'T REBOOTED MY LINUX MACHINE SINCE 1/19 - DO YOU THINK A REBOOT
> MIGHT HELP?)
Nope, and that would spoil your uptime record :-)
> Anyway, for all of the others that have run into slow copy times from
> WinXX to Linux/Samba, - Please let me know if you have found a FIX, or
> WORK AROUND.
> 
You could try installing Samba 2.2.0, there should be some RPMS on
samba.org.

It fixes a LOT of things, but I'm not sure about your particular
problem.

What are the network cards?  Are there collisions on the hub?

What do the logfiles say? 

Andrew Bartlett
-- 
Andrew Bartlett
abartlet@pcug.org.au

I'm sorry I can't be very helpful, but I am curious:

David Rankin wrote:
> THE PROBLEM:
> 
> Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named
> "Nemesis" - for good reason), the transfer speed slows to a
crawl. The
> Win95 copy dialog box starts out by saying 25 seconds remaining , then
> 60 seconds remaining, then 2 minutes, then 5 minutes, and so on.  I HAVE
> NEVER HAD THIS PROBLEM IN THE PAST.
Are you executing the commands from the Linux box or the Windows box (or
does the "from" imply the box you are executing
from)?
> 
> When I set up my server, I copied all of my firm's data from the Win95
> machine to "Nemesis" with no problem. Approximately 355 Meg
copied in ~
> 20 sec. (don't quote me on this, but it was less than a minute - after
> not having to reboot the Linux machine since 1/19, my memory fades -
> stupid human falability)
355 MB in 20 seconds is very fast -- are you sure that initial copy was
successful?  (I'd expect at best, on a 100 mhz Ethernet, closer to 40
seconds, and then I'd be impressed.  Are the 5 PCs connected to a hub or
a switch?  On larger networks connected by hub, it's common to get 40%
or less of the 100 mbps Ethernet as real "thruput".  If the initial
copy
wasn't successful, maybe that's part of the problem.  (But, if you made
the initial copy back on 1/19/01, you would have recognized the problem
before now.))

Good luck,
Randy Kramer

David Rankin wrote:
> 
> I never thought it would happen to me, but it did...
> 
> I have read threads about slow copies from WinXX to Linux/Samba on the
> list in the past, but I don't recall a concise answer regarding what
the
> cause was.
I don't have the answer for you, but hopefully I can help you with
debugging it. I'd really like to know what causes this before it happens
to me ;)
First off, please verify that it isn't the client causing the problem.
IOW: try the copy from win95, win98, ME, NT or whatever client your
using and make sure it is a problem on all of them (and a consistent
problem as well) You may have already done this, but you didn't say so,
so I'm bringing it up.
Check the samba log files for the clients that are having the problem.
Sometimes there's a big red flag there. If there isn't, trying
increasing the log level and see if something shows up.
If that doesn't uncover anything, run a tcpdump or ethereal capture on
the Linux box while causing the problem to occur. If you're not familiar
with debugging packet streams, I would suggest that you learn a bit
about it, since it's an invaluable debugging tool. Feel free to send
output to me if you have questions. Also (as stated by Andrew) verify
that the hub/switch isn't seeing a large number of collisions. Also run
ping back and forth for a while and make sure the connections are
reliable. (There have been a number of times when I've tried debugging
the heck out of a server only to finally discover that the CAT5 cable
wasn't reliable! doh!)
Try removing pptpd - especially if it's the only thing that you changed.
You may have introduced routing problems that are producing a lot of
packet traffic that's going the wrong way.
If none of that helps, try running top and/or systat while causing the
problem. See if your disk usage is maxed or your processer usage has
topped out. This may help direct you toward the problem's cause. Look
for memory usage as well - is the box swapping a lot? You may have a
process somewhere that's gone awry and started leaking memory, starving
the samba processes.
Then go back and do all these tests again! I'm serious. Human
fallibility, as you state, has caused me to miss many obvious things
because the boss was leaning over my shoulder insisting to know when the
problem would be fixed.

Most important, let us (on the list) know what fixes it.

Hope this helps,
Bill

Is this problem only seen with Samba? Try placing
the files in an FTP or HTTP share and then copy
them from there to your clients. I would suspect
some kind of physical network issue.

> I never thought it would happen to me, but it
did...
> 
> I have read threads about slow copies from WinXX
to Linux/Samba on the
> list in the past, but I don't recall a concise
answer regarding what the
> cause was.
> 
> THE PROBLEM:
> 
> Trying to copy an 8 meg file from Win95 to my
Linux/Samba box (named
> "Nemesis" - for good reason), the transfer speed
slows to a crawl. The
> Win95 copy dialog box starts out by saying 25
seconds remaining , then
> 60 seconds remaining, then 2 minutes, then 5
minutes, and so on.  I HAVE
> NEVER HAD THIS PROBLEM IN THE PAST.
> 
> I have tried reboots of the Win95 box -- no joy.
I have tried copying
> smaller files to Nemesis (~200k) no noticable
problem. I have tried
> copying large files from "Nemesis" to Win95 (or
Win98 or WinME)  and it
> screams (No Problem -- 1.5 meg so fast the copy
dialog doesn't even have
> time to appear). I need help, something is
amiss, at best, and FUBAR at
> worst.
> 
> When I set up my server, I copied all of my
firm's data from the Win95
> machine to "Nemesis" with no problem.
Approximately 355 Meg copied in ~
> 20 sec. (don't quote me on this, but it was less
than a minute - after
> not having to reboot the Linux machine since
1/19, my memory fades -
> stupid human falability)
> 
> MY SYSTEM:
> 
> Abit KT7/AMD 800 T-bird
> 256M Ram
> IBM 45G/7200 RPM ATA/66 drive
> Linux Mandrake 7.2 (stock ISO install)
> Samba 2.07 (Same stock ISO install)
> 
>     REST OF NETWORK: Win95, Win98, WinME (5
total)
> 
> CHANGES SINCE STOCK MANDRAKE INSTALL:
> 
> Loaded PopTop pptpd server
> Loaded xntp time sync program (xntp is not
currently running)
> 
> MY SMB.CONF
> 
>
#************************************************************
> # Samba config file created using SWAT
> # from localhost.localdomain (127.0.0.1)
> # Date: 2001/01/19 00:04:36
> 
> # Global parameters
> [global]
>  workgroup = RB_LAW
>  server string = RB_LAW Samba Server %v
>  encrypt passwords = Yes
>  update encrypted = Yes
>  smb passwd file = /etc/smbpasswd
>  passwd program = /usr/bin/passwd %u
>  passwd chat = *New*password* %n\n
*new*password* %n\n *success*
>  passwd chat debug = Yes
>  unix password sync = Yes
>  log file = /var/log/samba/log.%m
>  max log size = 50
>  name resolve order = wins lmhosts hosts bcast
>  socket options = TCP_NODELAY SO_RCVBUF=8192
SO_SNDBUF=8192
>  printcap name = lpstat
>  logon script = %U.bat
>  domain logons = Yes
>         time server = yes
>  os level = 34
>  preferred master = Yes
>  domain master = Yes
>  dns proxy = No
>  wins support = Yes
>  hosts allow = 192.168.7. localhost
>  min print space = 2000
>  printing = cups
>  print command = /usr/bin/lp -d%p -oraw %s; rm
%s
>  lpq command = /usr/bin/lpstat -o%p
>  lprm command = /usr/bin/cancel %p-%j
>  queuepause command = /usr/bin/disable %p
>  queueresume command = /usr/bin/enable %p
> 
> [netlogon]
>  comment = Rankin-Bertin logon services
>  path = /home/samba/logon
>  browseable = No
> 
> [Rankin-Bertin]
>  comment = Rankin-Bertin PLLC
>  path = /home/samba/rbpllc
>  valid users = @rbpllc
>  force group = rbpllc
>  admin users = david
>  writeable = Yes
>         map archive = Yes
>         inherit permissions = Yes
> 
> [homes]
>  comment = Homes Directory
>  writeable = Yes
>  browseable = No
> 
> [config] # ** I know this aint smart but I use
it daily -- so save the
> keystrokes (comment added for post to list)
>  comment = Admin Config Share
>  path = /
>  valid users = david
>         force user = root
>  force group = root
>  admin users = david
>  writeable = Yes
> 
> [Applications] # ** New share added 4/19 to hold
WinXX application
> programs (comment added for post to list)
>  comment = Windows Applications
>  path = /home/samba/winapps
>  valid users = @rbpllc
>  force group = rbpllc
>  admin users = david
>  writeable = Yes
>         map archive = Yes
>         inherit permissions = Yes
> 
> [printers]
>  comment = The Printing Army
>  path = /var/spool
>  guest ok = Yes
>  printable = Yes
>  printer = lp
>
#************************************************************
> 
> CHANGES TO SMB.CONF SINCE INSTALL
> 
> Addition of [Applications] share (as shown above
in the smb.conf)
> 
> QUESTION:
> 
> What in the world is causing the slow copy
behavior from my WinXX box to
> "Nemesis"? I don't get it! I can copy FROM
Nemesis to WinXX without any
> problems -- I just can't do it in reverse. In
the past I have sent 300+
> Meg of data to the server with no problem. Now
it stalls trying to copy
> anything bigger than ~200k from Windoze to
Linux. What should I check? I
> don't think 'pptpd' or 'xntpd' should have
anything to do with smb
> (xntpd isn't even running - pptpd is the only
new process running).  (I
> HAVEN'T REBOOTED MY LINUX MACHINE SINCE 1/19 -
DO YOU THINK A REBOOT
> MIGHT HELP?)
> 
> Anyway, for all of the others that have run into
slow copy times from
> WinXX to Linux/Samba, - Please let me know if
you have found a FIX, or
> WORK AROUND.
> 
> Thank You,
> 
> --
> David Rankin
> Nacogdoches, Texas
> 
> 
> 
> -- 
> To unsubscribe from this list go to the
following URL and read the
> instructions: 
http://lists.samba.org/mailman/listinfo/samba
> 

-

Randy Kramer wrote:
> I'm sorry I can't be very helpful, but I am curious:
>
> David Rankin wrote:
> > THE PROBLEM:
> >
> > Trying to copy an 8 meg file from Win95 to my Linux/Samba box (named
> > "Nemesis" - for good reason), the transfer speed slows to a
crawl. The
> > Win95 copy dialog box starts out by saying 25 seconds remaining , then
> > 60 seconds remaining, then 2 minutes, then 5 minutes, and so on.  I
HAVE
> > NEVER HAD THIS PROBLEM IN THE PAST.
>
> Are you executing the commands from the Linux box or the Windows box (or
> does the "from" imply the box you are executing from)?
> >
The Windows Box. Using windows explorer I am trying to move a couple of
directories from the Win95 machine to the new [Applications] share I created
on the Linux box "Nemesis"
>
> > When I set up my server, I copied all of my firm's data from the
Win95
> > machine to "Nemesis" with no problem. Approximately 355 Meg
copied in ~
> > 20 sec. (don't quote me on this, but it was less than a minute -
after
> > not having to reboot the Linux machine since 1/19, my memory fades -
> > stupid human falability)
>
> 355 MB in 20 seconds is very fast -- are you sure that initial copy was
> successful?  (I'd expect at best, on a 100 mhz Ethernet, closer to 40
> seconds, and then I'd be impressed.
I really flew. Everything copied perfectly.
>  Are the 5 PCs connected to a hub or
> a switch?
Cnet 10/100 8 port hub uplinked to a Linksys cable/dsl 4 port router for net
access. All WinXX clients and "Nemesis" plug into the hub.
> On larger networks connected by hub, it's common to get 40%
> or less of the 100 mbps Ethernet as real "thruput".  If the
initial copy
> wasn't successful, maybe that's part of the problem.  (But, if you
made
> the initial copy back on 1/19/01, you would have recognized the problem
> before now.))
Thanks Randy


--
David Rankin
Nacogdoches, Texas