On 28-Sep-05, at 11:10 AM, Jan Schaumann wrote:
> I have a file server, which regularly becomes unresponsive (via  
> network,
> normally responsive via console) and displays numerous warnings in the
> logs:
>
> WARNING: mclpool limit reached; increase NMBCLUSTERS
>
> I've already bumped NMBCLUSTERS twice, up to 65536 now.  options(4) is
> not very exhaustive of what the side effects (if any) may be of
> increasing this number.  How far can I bump this number?  What is
> affected by it?

I have a webserver that ran happily since Feb with 16384  
NMCLUSTERS... It suddenly started starving itself.  I'm running 65536  
now, and it's been fine for a couple of weeks but I'm confused by the  
sudden need as well.

Frankly, I've never even run this much so I don't know either...

Sorry, no help here but I'm commiserating with you.

I wish there was some way to deal with NMBCLUSTERS dynamically, or at  
the very least via sysctl... This has singlehandedly been the largest  
source of mid-night wakings for me over the years.