For a while now (2 months, and there has been no update or other change at the time the problem started, except some new clients went online) some /smbd processes constantly consume a full cpu core. sometimes there are also two such processes.
The system is freenas-9.10.1-U2 on a HP Microserver Gen8 with 16G RAM, 4 Disks as raidz2.
Upgrading to 9.10.2-U5 via the ISO did not change anything on this problem.
In this htop output it is the first process (53010) that consumes too much load. I do not know where it origins from.
All other processes disappear after short time which is the expected behavior.
Killing the problematic process breaks the samba services. Restarting samba revives the serving but also the problematic process.
From the reporting graphs I know the problem began 2 months ago and is present all the time (24/7). What makes it more mysterious is the fact that there is every morning between 7:40 and 8:00 a short period of 2-5 minutes where the cpu load returns to the expected levels. The system is up and running since 2.5 years now with absolutely no problem so far serving ~20 windows computers, some raspberries and 2 Macs.
The only suspicion I have (after trying for days all the tips and tricks I could find in forums and elsewhere without result) is that a specific client user or computer is causing this.
I did also scroll through the bug reports but could not find something useful, or something that solved the problem.
How can I determine which user/computer had invokes the specific samba process?
The server is responding fast and there is no other problem, but my suspicion is something must be wrong somewhere, and I can only sleep quite if it is solved.... :)
The system is freenas-9.10.1-U2 on a HP Microserver Gen8 with 16G RAM, 4 Disks as raidz2.
Upgrading to 9.10.2-U5 via the ISO did not change anything on this problem.
Code:
PID USER PRI NI VIRT RES S CPU% MEM% TIME+ Command 53010 root 52 0 288M 25464 S 25.4 0.2 11:29.31 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 53015 root 21 0 283M 24968 S 1.5 0.2 0:56.75 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 61799 hopfenmue 20 0 334M 28524 S 0.2 0.2 0:04.85 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 56241 twluxmsr 20 0 303M 26840 S 0.1 0.2 0:03.59 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 87267 root 20 0 302M 27092 S 0.0 0.2 0:02.20 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 35915 root 20 0 303M 26996 S 0.0 0.2 0:01.11 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 53040 root 20 0 303M 26652 S 0.0 0.2 0:00.37 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 94694 root 20 0 333M 27520 S 0.0 0.2 0:00.28 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 96641 root 20 0 302M 25976 S 0.0 0.2 0:00.13 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 53014 root 20 0 283M 24968 S 0.0 0.2 0:00.14 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 73679 root 20 0 303M 26684 S 0.0 0.2 0:00.12 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 18229 root 20 0 303M 26496 S 0.0 0.2 0:00.04 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf 31119 root 80 0 286M 25360 R 25.4 0.2 0:00.00 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf
In this htop output it is the first process (53010) that consumes too much load. I do not know where it origins from.
All other processes disappear after short time which is the expected behavior.
Killing the problematic process breaks the samba services. Restarting samba revives the serving but also the problematic process.
From the reporting graphs I know the problem began 2 months ago and is present all the time (24/7). What makes it more mysterious is the fact that there is every morning between 7:40 and 8:00 a short period of 2-5 minutes where the cpu load returns to the expected levels. The system is up and running since 2.5 years now with absolutely no problem so far serving ~20 windows computers, some raspberries and 2 Macs.
The only suspicion I have (after trying for days all the tips and tricks I could find in forums and elsewhere without result) is that a specific client user or computer is causing this.
I did also scroll through the bug reports but could not find something useful, or something that solved the problem.
How can I determine which user/computer had invokes the specific samba process?
The server is responding fast and there is no other problem, but my suspicion is something must be wrong somewhere, and I can only sleep quite if it is solved.... :)
Last edited:
