Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Oct 2008 02:17:38 -0700
From:      Jeremy Chadwick <koitsu@FreeBSD.org>
To:        Laszlo Nagy <gandalf@shopzeus.com>
Cc:        Johan Hendriks <Johan@double-l.nl>, freebsd-questions@freebsd.org
Subject:   Re: 7.1 hangs, shutdown terminated
Message-ID:  <20081010091738.GA27925@icarus.home.lan>
In-Reply-To: <48EF1C9C.3020201@shopzeus.com>
References:  <48EF14E1.9080808@shopzeus.com> <57200BF94E69E54880C9BB1AF714BBCB5DE18C@w2003s01.double-l.local> <48EF1C9C.3020201@shopzeus.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 10, 2008 at 11:13:00AM +0200, Laszlo Nagy wrote:
> Johan Hendriks írta:
>> If find / -sx is running and is consuming all CPU, what is the value of 
>> vfs.ufs.dirhash_mem: 
>>
>> # sysctl -a | grep dirhash
>>   
> shopzeus# sysctl -a | grep dirhash
> vfs.ufs.dirhash_docheck: 0
> vfs.ufs.dirhash_mem: 2095818
> vfs.ufs.dirhash_maxmem: 2097152
> vfs.ufs.dirhash_minsize: 2560
>
>> Make sure vfs.ufs.dirhash_mem: is not close to vfs.ufs.dirhash_maxmem:
>>   
> All right. It is close to it. Which one should I increase? I put this  
> into /etc/sysctl.conf:
>
>
> vfs.ufs.dirhash_maxmem=8228608
>
> Would it be scufficient?

We don't know, and can't tell you.  You'll have to monitor
vfs.ufs.dirhash_mem occasionally to see if you start to reach
vfs.ufs.dirhash_maxmem.

I have a tendency to use vfs.ufs.dirhash_maxmem=16777216, which is
16384*1024 (16MBytes).

I'm not fully confident this is what's causing your problem, but it's
definitely a recommendation by Johan.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081010091738.GA27925>