Stephan Pietzko <stephan.pietzko@uni-konstanz.de> wrote
>  
>  >  What does sysctl kern.mbuf.nmbclusters say? You could try increasing
>  >  that (in case this is not a leak but just high mbuf cluster demand).
>  
>  root@nepal:/root> sysctl kern.mbuf.nmbclusters
>  kern.mbuf.nmbclusters = 1024
>  
>  thats an idea, but i try first to reproduce the problem with the 
>  options         MBUFTRACE # Debuging the mclpl problem
>  and change the only one switch after an other.

Here a short info:
with the options MBUFTRACE i had the same problem one or two days
later (i mailed the logs). After that i increases
kern.mbuf.nmbclusters with options NMBCLUSTERS=16384. Now the machine
is running since 25 days and had served nearly 2TB without problems.

Donno if i solved the problem or just pushed the problem into a longer
timeperiod.

I will let the machine run long as possible and will give you the
result here.

so far Stephan Pietzko