Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Dec 2004 21:36:07 -0800
From:      Manfred Antar <null@pozo.com>
To:        Andre Guibert de Bruet <andy@siliconlandmark.com>, Dan Nelson <dnelson@allantgroup.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel)
Message-ID:  <6.2.0.14.2.20041207213333.03eb7298@pozo.com>
In-Reply-To: <20041208000849.D637@alpha.siliconlandmark.com>
References:  <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> <20041208050620.GG2629@dan.emsphone.com> <20041208000849.D637@alpha.siliconlandmark.com>

next in thread | previous in thread | raw e-mail | index | archive | help
At 09:15 PM 12/7/2004, Andre Guibert de Bruet wrote:

>On Tue, 7 Dec 2004, Dan Nelson wrote:
>
>>In the last episode (Dec 07), Andre Guibert de Bruet said:
>>>On Mon, 6 Dec 2004, Manfred Antar wrote:
>>>
>>>>I'm also seeing alot of :
>>>>Dec  6 10:06:53 pozo kernel: Accounting resumed
>>>>Dec  6 10:07:23 pozo kernel: Accounting suspended
>>>>Dec  6 10:07:38 pozo kernel: Accounting resumed
>>>>Dec  6 10:12:23 pozo kernel: Accounting suspended
>>>>Dec  6 10:12:38 pozo kernel: Accounting resumed
>>>>Dec  6 10:12:53 pozo kernel: Accounting suspended
>>>
>>>Ditto. Running accton all by itself to turn off accounting stops
>>>these cycles from occuring (Hardly a fix as you end up without logs
>>>to run reports from).
>>
>>It's a safety device that prevents accounting records from filling up
>>your hard drive in the event of forkbombs, configure scripts or other
>>things that cause high process turnover.  It's controlled by the
>>following sysctls:
>>
>>kern.acct_chkfreq: frequency for checking the free space (seconds)
>>kern.acct_resume: percentage of free disk space above which accounting resumes
>>kern.acct_suspend: percentage of free disk space below which accounting stops
>
>Noted. I am at a loss to see which of my filesystem it believes is running out of space. /var, the logical choice is not even at 10%:
>
>bling# df -h
>Filesystem     Size    Used   Avail Capacity  Mounted on
>/dev/ad4s1a    248M    125M    103M    55%    /
>devfs          1.0K    1.0K      0B   100%    /dev
>procfs         4.0K    4.0K      0B   100%    /proc
>/dev/ad4s1d    248M     14K    228M     0%    /tmp
>/dev/ad4s1e    3.9G    307M    3.3G     8%    /var
>/dev/ad4s1f    180G    6.1G    159G     4%    /usr
>/dev/ad6s1d    180G     20G    145G    12%    /mnt/misc
>/dev/amrd0a    265G     42G    202G    17%    /mnt/amrd0a
>/dev/ad0       226G    111G     97G    53%    /mnt/backups
>devfs          1.0K    1.0K      0B   100%    /var/named/dev
>
>Thanks!
>Andy

Same here I have over 19Gigs of free space.
It's something else a kernel from last Friday does not do this.

==================================
||      null@pozo.com           ||
||      Ph. (415) 681-6235      ||
================================== 



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