lkml.org 
[lkml]   [1999]   [Feb]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.2.1 TCP problems. (smbfs and ftp.)

Hi,

When running 2.2.1 smbfs (samba 2.0.0 smbmount binaries) and RH 5.1
/usr/bin/ftp , my data connections run up very big Send-Q's.

The ftp data connections run up a big send-Q and then just sit there.
Until killed. The samba connections run up big send-Q's but data gets
through at a decreasing rate, until it's mostly dead too...

-----excerpt of netstat -t -------------------
tcp 0 0 usel:1368 ekoed1:ftp ESTABLISHED
tcp 0 58400 usel:1370 ekoed1:ftp-data ESTABLISHED
tcp 0 87600 usel:1212 ekohrp:ftp-data CLOSE
tcp 0 58400 usel:1302 ekoed1:ftp-data CLOSE
tcp 0 0 usel:1355 ekohrp:ftp ESTABLISHED
tcp 0 116800 usel:1356 ekohrp:ftp-data ESTABLISHED
-----------------------------------------------
notice 2 killed ftp sessions in CLOSE state.
------dmesg-----------------------------------
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_trans2_request: result=-32, setting invalid
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_trans2_request: result=-32, setting invalid
smb_retry: signal failed, error=-3
smb_file_read: 10.X/PHCO_8934 validation failed, error=-32
smb_retry: signal failed, error=-3
smb_get_length: recv error = 104
smb_trans2_request: result=-104, setting invalid
smb_retry: signal failed, error=-3
smb_get_length: recv error = 512
smb_trans2_request: result=-512, setting invalid
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_lookup: find //Soundtrack failed, error=-5
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
smb_retry: signal failed, error=-3
smb_lookup: find //olle failed, error=-5
-----------------------------------------------
notice the //xxx in "smb_lookup: find //xxx failed" are names of top level
directories in the mounted share.
System: Compaq Deskpro 5xxx 3com 3C590 10base-T Pretty much vanilla RH 5.1
Ftp was putting stuff on HP-UX 10.20 machines (unloaded).
Samba was putting files on a vanilla NT-4.0-server.


/olle

----
God is real, until declared integer.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [from the cache]
©2003-2011 Jasper Spaans