[Samba] Problem: Copying large amount of files to SAMBA Server. W2KError "file in use" for exe files

[Jon Gerdes]

At the risk of stating the obvious but 2.2.3a is rather old - try updating to the latest stable 2.2.x series of Samba.  After that you might want to look into the options relating to "Oplocks"

>>I am wondering if anybody has expected the same problem before?
The only idea i have is that this error occures because i have a lot of
file and directory, chown, chmod directives in my share definiton and that
maybe the machine is too slow to workup all the requests.
But the thing that speaks against that is that the total CPU usage normally doesnt
go higher than 40%.

In my experience Samba deals very well with seriously high loads even on reasonably modest hardware.  I have a dual PIII 600 with 2GB RAM being constantly wacked by around 800 concurrent connections.  Performance is excelent considering the load.  Oh and there's an Apache, QMail with virus scanning, NetSaint etc etc

Cheers and greeting from the UK
Jon

>>> "Grand Apeiron" <Grand.Apeiron at gmx.net> 30/05/2003 12:28:37 >>>
Hi all,

first i want to say a big "Hello" to the list, since this is my first posting here.

Yesterday i just installed another SAMBA server on a middle class (K6-2 500, 128MB)
machine.
All shares are accessable like expected but i often get an
"Can't move file. File in use." error from my W2K client when moving large
amount of files to the SAMBA server.
This error only happens for *.exe files.
Normally i am able to move the exe files to the samba server on the second try
but that error is very annoying since i am not able to move large amount of
files unattended.

The SAMBA version is 2.2.3a. The host system is debian with kernel 2.4.20.
The shares are laying on XFS filesystems.

I am wondering if anybody has expected the same problem before?
The only idea i have is that this error occures because i have a lot of
file and directory, chown, chmod directives in my share definiton and that
maybe the machine is too slow to workup all the requests.
But the thing that speaks against that is that the total CPU usage normally doesnt
go higher than 40%.

Heres a share defintion example from my smb.conf.

   #< Share for FTP Data#######################################################
      [FTP]
         comment     = FTP Data Directory
         path        = /var/provide/dataserv/ftp
         guest ok    = no
         valid users = @ftpusers
         write list  = @ftpadmins @ftpwriters
         browseable  = yes
         read only   = yes
         create mode = 0664
         directory mode = 7774
         force create mode = 0664
         force directory mode = 7774
         force group = ftpusers
         force user  = ftp
   #> Share for FTP Data#######################################################


Thanx in advance for any tips or hints.
With greetings from germany,
Grand Apeiron

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba