Some more testing indicates that the problem is most likely in close, not mmap.
I modified the program to the following:
zool# more test.c
#include stdio.h
#include fcntl.h
#include string.h
#include stdlib.h
#include errno.h
#include sys/mman.h
int main (int argc, char *argv[])
{
int
On 30 July 2015, at 01:39, Doug Hardie bc...@lafn.org wrote:
On 29 July 2015, at 23:44, Peter Jeremy pe...@rulingia.com wrote:
[reformatted]
On 2015-Jul-29 17:41:33 -0700, Doug Hardie bc...@lafn.org wrote:
I have several FreeBSD 9.3 systems that are using swap and I can’t
figure out
On 29 July 2015, at 23:44, Peter Jeremy pe...@rulingia.com wrote:
[reformatted]
On 2015-Jul-29 17:41:33 -0700, Doug Hardie bc...@lafn.org wrote:
I have several FreeBSD 9.3 systems that are using swap and I can’t
figure out what is doing it. The key system has 6GB swap and
currently it
On 29 July 2015, at 17:41, Doug Hardie bc...@lafn.org wrote:
I have several FreeBSD 9.3 systems that are using swap and I can’t figure out
what is doing it. The key system has 6GB swap and currently it has over 2GB
in use. ps shows only a kernel module [intr] with a W status. Obviously
[reformatted]
On 2015-Jul-29 17:41:33 -0700, Doug Hardie bc...@lafn.org wrote:
I have several FreeBSD 9.3 systems that are using swap and I can’t
figure out what is doing it. The key system has 6GB swap and
currently it has over 2GB in use.
Is the system currently paging (top(1) and systat -v
I have several FreeBSD 9.3 systems that are using swap and I can’t figure out
what is doing it. The key system has 6GB swap and currently it has over 2GB in
use. ps shows only a kernel module [intr] with a W status. Obviously that
isn’t using the space. No other process shows a W in its
shouldn’t use swap. How do I figure out what that swap space is being used
for?
Maybe top(1)?
top -P
for example. At least you could see who's chewing all your memory. Which
should be a good clue as to who's responsible for swap usage.
UFS although I don’t see how that could make a difference
for?
Maybe top(1)?
top -P
for example. At least you could see who's chewing all your memory. Which
should be a good clue as to who's responsible for swap usage.
--Chris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman
ID: 0
cpu1 (AP): APIC ID: 1
After upgrade swap usage increased dramaticly - from 5% on 5.4 to 20%-70% on
6.0. Small investigation showed me that apache is responsible, but even
recompiling it doesn`t help. I can restart apache every 4 hours, but maybe
someone can show me nicer way to deal
