The Samba-Bugzilla – Bug 13267
smbd deadlock/endless wait or endless loop
Last modified: 2018-02-16 15:58:37 UTC
i have a big problem with smbd. in some situations, smbd hangs at a waitpoint (futex wait) and the only thing i can do, is killing all processes, securly smbd and nmbd) with killall -9 smbd nmbd to restart the services.
my server is a amd-system with 8 cores.
yesterday, i must make this two times.
i think the trigger for this bug have something to do with the usage of the server.
yesterday i transfer files to a linux-system with a 2.6 kernel and a windows-system with xp, both with the maximal transferrate the systems can use, in sum ca. 30 MB/s.
in the moment, i open some files on xp too, the server hangs the first time and later a second time.
if i remeber right, i tried samba to version 4.7.3 or 4.7.4 with the same problems.
i have this problem with samba since my last update in september 2017 after more then one year without updates.
at the most time, only on system will get or send data and the server works fine. bat every time i transfer data to my archive-system or verify and delete some backups on the system over samba (normaly i use rsync to update the archive) and read files from xp at the same time, my samba-server hangs.
i don't know why this happen. it is possible, that some parallel used functions make the problem in combination with the multiprocessor-system or a missing network package or signal while there is no timeout programed.
i have no such problems with version less then 4.x! on my old systems, i use samba 3.6.25.
i don't remember the last used version on the newer systems, but i think it was a version less then 4.x. i think, it must be 3.6.23 or an other 3.6.2x.
if it is impossible to correct this bug, i must install the old version 3.6.25 or latest 3.6.x on my new server instead of the 4.x version.
Please upload a gstack of the hung process. Also, your kernel seems to be pretty vintage. Please try setting
dbwrap_tdb_mutexes:* = false
in the [global] section in your smb.conf
i try it. but today the server hangs again.
this config line don't solve the problem.
Well, what can I say here. I don't think with direct access to the system in that state we can solve this. You should get someone from https://samba.org/samba/support, them sign an NDA and give them root access to your system. This can have a *LOT* of reasons, from Hardware problems to kernel bugs to Samba itself.
typo in my last comment: I don't think we'll solve this *without* direct system access