[Samba] every increasing connection count followed by load # overload

[Michael Joyner]

I am having a bizarre problem with a samba server here at Edward Waters 
College.

Hopefully someone can give me insight to inform me what to look for.

samba version = 3.0.14a
SuSE 9.1, up-to-date-via-apt
AD/W2K3 (no sp)
Winbind using RID algorithm

server purpose: HOMES, DESKTOPS, MY DOCUMENTS, PROFILES
Quotas are: ON
Filesystem: Reiser
HW Raid 5 (MegaRaid)

4 logical processors (dual+ht).
uname -a:

Linux ewc05 2.6.5-7.151-smp #1 SMP Fri Mar 18 11:31:21 UTC 2005 i686 
i686 i386 GNU/Linux

If the number of connections exceeds 155 (per samba counting), the 
system load quick escalates to like 700+, and the user count also 
suddenly skyrockets. a majority of the samba processes seem to get stuck 
in state "D"

inode count usage is unrealisticically high. :)

I deleted all the samba db files, no change.

If I put in a max connections limit of 155, it doesn't "fork bomb".

Where should I start looking?

-mjoyner at ewc.edu/mjoyner at vbservices.net