Lately I got my disk overfilled (0 bytes free) and Samba was still running. When I tried to log into machine, it took me very long, so I ran top and soo that the system load is above 40, that there are many nmbd processes running, which take a great proportion of CPU. I know that a full disk is not a good state for a system, but having extremely big load because of it makes such disasters even worse.
This doesn't make a lot of sense to me. Why were there numerous nmbd processes? Without some more information such as what state they were in (gdb bt) or something else this is pretty impossible to track down. Are you running nmbd from inet? or as a daemon ? Is nmbd acting as a wins server? Was the Samba box the local master browser? Domain master browser? etc... just need a lot more information.
Well, I've no idea why there were so many nmbd processes, and hence the bug report. This machine is a PDC, nmbd and smbd are run as daemons. nmbd is acting as a Wins server and a domain master, but it wasn't a local master.
do yo have 'dns proxy = yes'? IIRC it is the default.
Well, I don't have any "dns proxy" entries in my smb.conf. So if it is set to "yes" by default when no "dns proxy" occurs in smb.conf, than yes, I have it set.
corner case. Hopefully will get back to it and research more.