beefy system exhausted by MRTG port install (Cannot allocate
memory)
Eric Anderson
anderson at freebsd.org
Tue Feb 20 15:30:30 UTC 2007
On 02/19/07 22:20, Arone Silimantia wrote:
> New, modern, p4-xeon based system.
>
> 4 GB physical RAM:
>
> # dmesg|grep emory
> real memory = 3489071104 (3327 MB)
> avail memory = 3418656768 (3260 MB)
>
> 4 GB swap:
>
> # swapinfo
> Device 1K-blocks Used Avail Capacity
> /dev/da0s1b 4194304 40 4194264 0%
>
> And because it has a multi-TB filesystem attached, it even has a big number here:
>
> # cat /boot/loader.conf
> kern.maxdsiz="3072000000"
>
> So imagine my surprise when I:
>
> # cd /usr/ports/net-mgmt/mrtg ; make install
>
> (snip, snip)
>
> ===> Patching for png-1.2.12_1
> ===> Applying FreeBSD patches for png-1.2.12_1
> ===> Configuring for png-1.2.12_1
> ===> Building for png-1.2.12_1
> cc -O2 -fno-strict-aliasing -pipe -c png.c
> cc -O2 -fno-strict-aliasing -pipe -c pngset.c
> cc -O2 -fno-strict-aliasing -pipe -c pngget.c
> cc -O2 -fno-strict-aliasing -pipe -c pngrutil.c
> cc -O2 -fno-strict-aliasing -pipe -c pngtrans.c
> cc -O2 -fno-strict-aliasing -pipe -c pngwutil.c
> cc -O2 -fno-strict-aliasing -pipe -c pngread.c
> cc -O2 -fno-strict-aliasing -pipe -c pngrio.c
> cc -O2 -fno-strict-aliasing -pipe -c pngwio.c
> cc -O2 -fno-strict-aliasing -pipe -c pngwrite.c
> cc -O2 -fno-strict-aliasing -pipe -c pngrtran.c
> virtual memory exhausted: Cannot allocate memory
> *** Error code 1
>
>
> after this attempt, swapinfo still shows zero swap in use.
>
> What does this mean ?
>
> Is my system now in an unstable state ? Should I reboot ?
Did you try reducing your maxdsiz to something a few hundred mb's less?
Eric
More information about the freebsd-hackers
mailing list