[Samba] CPU consumption by samba

[Wolfram Quester]

Hi,

I'm no expert at all and I never experienced something like that, so
probably I'm the wrong to ask. Perhaps someone more experienced on the
list could help?

On Sat, Jun 21, 2003 at 11:29:22PM +0200, Massimiliano Hofer wrote:
> Alle 9:03 AM, mercoledì 18 giugno 2003, Wolfram Quester ha scritto:
> 
> > I remember that there were issues with VisualFox Pro and oplocks
> > discussed on this list. Try to disable them
> > A recommendation was to look at
> > http://www.drouillard.ca/Tips&Tricks/Samba/Oplocks.htm
> > You can search this list at marc.theaimsgroup.com for "Foxpro Test" with
> > http://marc.theaimsgroup.com/?l=samba&w=2&r=1&s=Foxpro+Test&q=b
> > for further information.
> 
> Thank your for the interesting links, but they seem to discuss corruption 
> problems (which I don't have).
Sorry for leading you on the wrong path. The term VisualFox Pro just
rang a bell. 

> Anyway I managed to perform some more tests with various settings of locks, op 
> locks, caching, etc. The only significant parameter (if I'm not missing 
> anything fundamental) I didn't test extensively is the lock spin, which I'll 
> test in the next few days.
> I even tried samba 3, but to no avail (it was slower).
> Sometimes it got a little faster or slower, but the loading time never went 
> below 30 seconds and this is way too slow compared with 2 seconds on a 
> Windows 2000 server. Meanwhile all other application run faster with samba 
> than with Windows (as expected :)).
> 
> During those 30 seconds the CPU load takes 80% user time and 20% system time 
> and this is with just one client. What could possibly take this much 
> resources?
I first thought on some protocol negotiation, but this should show up on
logon time, not during a working connection.

In your log there are quite a lot of lines like
> [2003/06/13 19:43:13, 3] smbd/trans2.c:call_trans2qfilepathinfo(1719) call_trans2qfilepathinfo: vfs_stat of vfcssrc failed (No such file or directory)
> [2003/06/13 19:43:13, 3] smbd/error.c:error_packet(94) error string = No such file or directory
> [2003/06/13 19:43:13, 3] smbd/error.c:error_packet(113) error packet at smbd/trans2.c(1721) cmd=50 (SMBtrans2) NT_STATUS_OBJECT_NAME_NOT_FOUND
> [2003/06/13 19:43:13, 3] smbd/process.c:process_smb(878) Transaction 10280 of length 88
They make me think there might be issues with some name-mangling or
codepage-settings. Are there accents, umlauts or the like in your
filenames? The interesting part would be why these things don't occur
with other applications then.

Best regards,

Wolfi