I have noticed that when I access my Samba share from Windows, the
smbd daemon will always use aprox 10-20% CPU - no matter if the share is used or not from Windows. Even if I close the share/window,
smbd will continue using CPU and only a reboot/shutdown of my Windows can get the CPU usage down to normal.
This is when I have just rebooted/started my Windows - the share is mapped but not accessed yet. It will have this "red" status in Windows until I access it:
Before I do anything else I check the
top on my Linux:
There is no problem so far - the CPU usage is not noticable at all in
top so everything is still good.
BUT ... when I then access the share from Windows, the Linux CPU immediately raises to 10-20%:
smbstatus always shows some locked(?) files which for sure(?) is not accessed from my Windows:
testparm shows my
The only way I can "fix this" is by either rebooting my Windows or unmap the drive/share.
One more strange thing - when I have unmapped the share/drive, I can of course still access the share via UNC... and when accessing it through UNC it does NOT raise the CPU at all!? Weird!
My hardware is quite recent/uptodate:
Server: Core i5 1.5-2.9GHz dual core/HT 16GB RAM Samsung 850 Pro (512GB)
Client: Windows 8.1
I have used the same configuration on a CentOS 6 installation without any problems. I have also tried disabling whatever I think can communicate with the network share on my Windows computer (antivirus and backup software).
Can anyone help nailing this problem down?