Windows 98 Stalls When Copying Large Files to Samba cvs HEAD

Alex Satrapa alex at topic.com.au
Thu Jun 10 07:06:28 GMT 1999


Sorry for the false alarm people.

While checking configurations of Samba/Solaris, it occured to me that
the problem might actually exist within the setup of my Windows 98
client (what a novel concept that Windows might be broken).

Sure enough, my machine had spontaneously added two devices representing
my network card, both with TCP/IP functionality. So now I've suddenly
fixed a whole swathe of problems with my machine that didn't involve
Samba at all.

BTW - thanks for the people who offered support. For future reference,
if you're looking for "strace" and you're working on Solaris, what you
really want is "truss".

Anyhow, I've chewed enough bandwidth already.
Alex

Alex Satrapa wrote:
> 
> I've been having endless troubles copying files from a Windows 98
> machine to a Samba share.
> 
> The file that's the victim of the problem is a 28k HTML file called
> "Section1.html". I've copied other files with no problem - everything
> from 120b to 9kb. It seems that Samba/Win98 is choking on large files.
> 
> I've tried to find the cause of the problem, but since I'm in totally
> unfamiliar territory (I'm a PERL scripter, not a C programmer, and I
> haven't much of a clue how Samba works internally), I finally admit
> defeat. I'm sure there's something wrong with either some obscure
> registry entry in my Windows 98 machine, or something about the way the
> Samba source was configured before it was compiled. Sorry, I don't have
> the exact options at hand.
> 
> I've tried different settings for oplocks and strict sync. Can you tell
> that I haven't got a clue? :)  The problem remains (nothing changed that
> I noticed - the problem stayed exactly the same).
> 
> If anyone has even "stab in the dark" suggestions, I'd like to hear
> them!
> 
> Windows sits there saying "8 minutes remaining" for about two minutes,
> then aborts the copy with the following error message:
> 
> "Cannot create or replace Section1: The specified network resource or
> device is no longer available. [OK]"
> 
> Samba reports the following at log level 5:
> [1999/06/09 10:55:02, 5] smbd/mangle.c:name_map_mangle(982)
>   name_map_mangle() ==> [tpacoo]
> [1999/06/09 10:55:02, 4] smbd/dir.c:DirCacheAdd(678)
>   Added dir cache entry BEP-CD/HUMAN_SOLUTIONS_DATA/www.accc.gov.au
> TPACOO -> tpacoo
> [1999/06/09 10:55:02, 5] smbd/filename.c:unix_convert(634)
>   conversion finished
> BEP-CD/HUMAN_SOLUTIONS_DATA/WWW.ACCC.GOV.AU/TPACOO/Section1.html ->
> BEP-CD/HUMAN_SO
> LUTIONS_DATA/www.accc.gov.au/tpacoo/Section1.html
> [1999/06/09 10:55:02, 5] locking/locking_shm.c:shm_get_share_modes(119)
>   get_share_modes hash bucket 6 empty
> [1999/06/09 10:55:02, 5] lib/util.c:show_msg(496)
>   size=35
>   smb_com=0x6
>   smb_rcls=0
>   smb_reh=0
>   smb_err=0
>   smb_flg=128
>   smb_flg2=1
> [1999/06/09 10:55:02, 5] lib/util.c:show_msg(502)
>   smb_tid=1
>   smb_pid=5937
>   smb_uid=100
>   smb_mid=39810
>   smt_wct=0
> [1999/06/09 10:55:02, 5] lib/util.c:show_msg(512)
>   smb_bcc=0
> 
> Regards
> Alex Satrapa


More information about the samba-ntdom mailing list