[Samba] 3.0.21c and big wmv or mpg files

Thomas Bork tombork at web.de
Wed Apr 5 21:16:09 GMT 2006

Tom Peters wrote:

>> While copying the wmv test file a have a cpu utilization of 95! 
>> percent (top) of smbd at the time, samba creates the sparse (?) file 
>> in the size needed for the test file.
> I don't believe this happens in my case. I am not certain. I know that 
> when it fails, Windows clients see a 0 bytes file with the name of the 
> destination in the target share. You have to erase or overwrite it when 
> you try again.

The high cpu utilization in our test case is caused of using quotas and 
an correspondending entry in smb.conf:

strict allocate = yes

Received a partially log from a user with a lot of

[2006/04/05 16:51:58, 3] smbd/error.c:error_packet(146)
   error packet at smbd/notify.c(55) cmd=160 (SMBnttrans) NT code 0x0000010c

>> Maybe this is problematical on smaller systems. Samba is running here 
>> on an VMWARE on top of XP (the test client) with P4 3,2 GHz:

One user tested without

strict allocate = yes

and can copy the file now.
Another user tested with more memory in his machine (celeron 1GHz, at 
first with 128 MB, then with 512 MB) and with

strict allocate = yes

and can copy the file now - but needs 50 minutes to copy this file...

der tom

More information about the samba mailing list