4.1.7 Slow To Respond To SMB Network Discovery...

Jedi Knight wrote:
I wasn't able to reproduce the issue with my Mac 10.6.5, Windows XP and Windows Vista via GigE LAN. If you guys can send in the system logs, it may give us some clue here.

Hi,
I already checked the logs and they are silent. Even trying to bump the smb.conf log level didn't yield much. So far, I have managed to get strace onto the box (not trivial since the 64-bit and 32-bit versions are obnoxiously glommed into the same .deb), but it doesn't seem to work exactly correctly wrt the "-f" follow flag (it doesn't follow the children), so I was having to manually attach and trace the children. What I thought I saw during the enumeration were attempts to connect to two addresses that are not active (or even valid for my home subnet) viz something like 10.1.1.6 and 10.1.1.7, which eventually time out. I'm starting to wonder if there's some stale information in a tdb file somewhere.

Anyway, it seems the slow enumeration issue isn't the same problem as the inability to connect from a Linux cifsfs client. In the later case, as documented elsewhere on the forums, if you simply ssh in and restart the Samba, the problem goes away.

I'll work on the debugging again in a few days. Currently busy porting stuff from 2.6.18 to 2.6.32 (fun).

Oh, and I think the Mac issue is yet a third problem. I have no performance problems from either Windows or Linux *once* I am connected, but enumeration is dog-slow, and Linux cannot connect unless I restart Samba after the NV is rebooted.