Please include the following to bug ID: 26222 at:

http://bugs.samba.org/?findid=26222 




More checking shows that closing a search window on
Windows in the middle of it's search doesn't stop the
SMB activity. Network utilization remains high, and it
seems as if the server is stuck searching.

In an attempt to verify, I created a share on Win2k,
and followed the same procedure:
Server: Win2k Client: the same Win XP
1. Map a network drive to a directory that has about 4
gig of data.
2. Do a search for a file.
3. In the middle of searching, I close the search
window, without pressing a stop button.
4. The session between WinXP and Win2k closes
properly.

Doing the same thing between WinXP client and Samba
server (same as below), the connection remains open,
even after I close the search window. Network
utilization remains high.


-----------------------------------------------------
ORIGINAL BUG REPORT FOLLOWS:
-----------------------------------------------------



homes# /home/samba/sbin/smbd -V
Version 2.2.6
homes# gcc -v
Using builtin specs.
gcc version 2.95.4 20020320 [FreeBSD]
homes# uname -a
FreeBSD homes.xxxxx.xxx 4.7-RELEASE FreeBSD
4.7-RELEASE #0: Thu Dec 12 04:05:20 PST 2002    
[EMAIL PROTECTED]:/usr/src/sys/compile/DAN_QS  i386
homes# 

Client: Windows XP Pro. UNder TCP/IP properties for
that interface:

Client for Micorosoft Networks
File and Printer Sharing for Microsoft Networks
Network Monitor Driver
TCP/IP




1. Mapped a drive to the samba share (my home
directory on samba) as Z:

2. Mapped "My Documents" to Z:, which is mapped to my
home directory, defined in smb.conf as /home/$u

2. Did a "search for | files " from a Windows XP host.

3. Search started and then after a while, the SMB
storm started. Network utilization jumped from <1% to
>12%.

4. Using Ethereal, I collected 1 seconds of data,
which yielded 2833 packets (all Samba related).

5. Windows was stuck searching on 1 large zipped file
of html documents (file zie = 105 MB), at which time,
the network utilization increased, and remained that
way.

6. Then, did the following as root on the fileserver:


homes# ps -aux | grep nmb
root   3817  0.0  0.3  2832 1464  ??  Ss   Sat02PM  
0:12.83 /home/samba/sbin/nmbd -D
root  12067  0.0  0.0   336  136  p0  RL+   1:36PM  
0:00.00 grep nmb
homes# kill -HUP 3817

still storming..

homes# kill 3817
homes# ps -aux | grep nmb
homes# ps -aux | grep smb
win   12019 13.2  0.7  5320 3464  ??  S    12:37PM  
1:30.67 /home/samba/sbin/smbd -D
root   3813  0.0  0.4  3788 1812  ??  Is   Sat02PM  
0:00.06 /home/samba/sbin/smbd -D
homes# kill -HUP 12019

still storming..

homes# kill 12019
homes# ps -aux | grep smb
root  12072  4.9  0.4  4440 2148  ??  S     1:37PM  
0:00.47 /home/samba/sbin/smbd -D
root   3813  0.0  0.4  3788 1812  ??  Ss   Sat02PM  
0:00.06 /home/samba/sbin/smbd -D
homes# kill -HUP 3813

stopped storming..

homes# /home/samba/sbin/nmbd -D

storming again...

homes# ps -aux | grep nmb
root  12076  0.0  0.3  2816 1576  ??  Ss    1:37PM  
0:00.01 /home/samba/sbin/nmbd -D
homes# kill 12076

still storming...

homes# ps -aux | grep smb
win   12072 11.3  0.4  4176 2176  ??  S     1:37PM  
0:07.06 /home/samba/sbin/smbd -D
root   3813  0.0  0.4  3788 1848  ??  Is   Sat02PM  
0:00.06 /home/samba/sbin/smbd -D
homes# kill -HUP 3813

still storming...

homes# kill 3813

stopped...

homes# /home/samba/sbin/smbd -D

no storming now. 

homes# ps -aux | grep mbd
root  12082  0.0  0.4  3788 2208  ??  Is    1:39PM  
0:00.00 /home/samba/sbin/smbd -D
homes# /home/samba/sbin/nmbd -D
homes# still ok...

homes# now i am accessing a share...all back to
normal. can access the share as usual.


# Samba config file created using SWAT
# from xpeecee.xxxxx.xxx (192.168.0.1)
# Date: 2002/12/20 14:06:24

# Global parameters
[global]
        workgroup = XXXNET
        netbios name = HOMES
        server string = homes
        interfaces = 192.168.0.14
        bind interfaces only = Yes
        encrypt passwords = Yes
        preferred master = No
        local master = No
        domain master = No
        guest account = 
        wide links = No

[homes]
        comment = %u's home directory.
        path = /home/%u
        read only = No
        create mask = 0750
        directory mask = 0750
        browseable = No

[users1]
        comment = Group directory - users1
        path = /home/public/users1
        valid users = @users1
        read only = No
        create mask = 0770
        security mask = 0770
        directory mask = 0770
        directory security mask = 0770


homes# set
_

addsuffix
argv    ()
cwd     /root
dirstack        /root
echo_style      bsd
edit
filec
gid     0
group   wheel
history 100
home    /root
killring        30
loginsh
mail    /var/mail/root
owd
path    (/sbin /bin /usr/sbin /usr/bin /usr/games
/usr/local/sbin /usr/local/bin /usr/X11R6/bin
/root/bin)
prompt  homes# 
prompt2 %R? 
prompt3 CORRECT>%R (y|n|e|a)? 
savehist        100
shell   /bin/csh
shlvl   1
status  0
tcsh    6.12.00
term    vt100
tty     ttyp0
uid     0
user    root
version tcsh 6.12.00 (Astron) 2002-07-23
(i386-intel-FreeBSD) options
8b,nls,dl,al,kan,sm,rh,color,dspm,filec
homes# setenv
USER=root
LOGNAME=root
HOME=/root
MAIL=/var/mail/root
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin
TERM=vt100
BLOCKSIZE=K
FTP_PASSIVE_MODE=YES
SHELL=/bin/csh
SSH_CLIENT=192.168.0.1 1350 22
SSH_TTY=/dev/ttyp0
HOSTTYPE=FreeBSD
VENDOR=intel
OSTYPE=FreeBSD
MACHTYPE=i386
SHLVL=1
PWD=/root
GROUP=wheel
HOST=homes.xxxxx.xxx
REMOTEHOST=xpeecee.xxxxx.xxx
EDITOR=vi
PAGER=more


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Reply via email to