lang/gcc and tmpfs no space let on device
marko.cupac at mimar.rs
Fri May 16 13:40:32 UTC 2014
On Fri, 16 May 2014 06:11:21 -0700
David Wolfskill <david at catwhisker.org> wrote:
> * I've been using 2G tmpfs for some time without issue.
> * The above error messages may be misleading: it is *possible* that
> the actual complaint is not lack of space, but lack of available
> inodes -- you can't tell from the message alone. "df -i /tmp" is
> likely to be helpful in diagosing what is actually the problem.
It is not related to inodes, confirmed by appending output of df -ih to
a file by means of cron job that runs every minute:
tmpfs 128M 388K 128M 0% 39 459k 0% /tmp
tmpfs 128M 468K 128M 0% 41 459k 0% /tmp
tmpfs 128M 452K 128M 0% 41 459k 0% /tmp
tmpfs 128M 476K 128M 0% 57 459k 0% /tmp
tmpfs 128M 480K 128M 0% 45 459k 0% /tmp
tmpfs 128M 504K 128M 0% 46 459k 0% /tmp
tmpfs 128M 17M 111M 13% 2.5k 456k 1% /tmp
tmpfs 128M 18M 110M 14% 50 459k 0% /tmp
tmpfs 128M 39M 89M 30% 72 459k 0% /tmp
Somewhere in 10th minute it fills up /tmp which breaks building,
and whatever build process created in /tmp is removed.
This is the point of failure:
libtool: compile: /usr/ports/lang/gcc/work/build/./gcc/gcj
-fomit-frame-pointer -Usun -fclasspath=
--encoding=UTF-8 -Wno-deprecated -fbootstrap-classes -g -O2 -c
-MT javax/management.lo -MD -MP -MF javax/management.deps
@javax/management.list -fPIC -o javax/.libs/management.o jc1: fatal
error: error writing to /tmp/ccmi9d4D.s: No space left on device
I'll try to increase /tmp to 512Mb and see what happens.
More information about the freebsd-ports