/usr/obj is 11GB huge on FreeBSD 12-current

Wolfram Schneider wosch at freebsd.org
Fri Dec 15 17:39:05 UTC 2017

On 15 December 2017 at 17:51, Wolfram Schneider <wosch at freebsd.org> wrote:
> On 15 December 2017 at 13:02, David Wolfskill <david at catwhisker.org> wrote:
>> On Fri, Dec 15, 2017 at 10:12:09AM +0100, Wolfram Schneider wrote:
>>> Hi,
>>> I upgraded a machine from 11-stable to 12-current. The /usr/obj tree
>>> is now 11GB huge:
>>> FreeBSD 12-current
>>> $ du -hs /usr/obj
>>>  11G /usr/obj
>>> on FreeBSD 11-stable it was less the size:
>>> $ du -hs /usr/obj
>>> 5.6G /usr/obj
>>> this is a problem when you have a small VM with 20GB disk space or less.
>>> Is there a way to use less /usr/obj disk space during build? I know
>>> that we have to do some bootstrapping for newer compiler tools, but
>>> does we need to keep all temp files during the build?
>> There was a change near the beginning of November; please see UPDATING
>> entry 20171101 -- you probably have several no-longer-used
>> subdirectories under /usr/obj/usr/src/.
>> Once those are cleared out, my experience (tracking stable/11 & head in
>> different slices on the same machines) is that stbale/11 is using about
>> 5.0G, while head uses about 6.1G.
> I think the suspect directories are "tmp" and "obj-lib32", together
> they are 4.1GB huge.
> I will run a build of current again with a clean obj tree (-current on
> a recent -current). Let's see.

I run a test on universe12b (FreeBSD 12.0-CURRENT #0 r325426: Sun Nov
5) with an empty obj directory.

`make buildworld' creates 9.7GB of obj data. After running `make
buildkernel' it will grow to 12GB. This is on a ZFS filesystem (my
original report was on UFS)


> Can we agree that the obj tree should not grow from 5GB to 10GB for
> the next release?
> -Wolfram
> --
> Wolfram Schneider <wosch at FreeBSD.org> https://wolfram.schneider.org

Wolfram Schneider <wosch at FreeBSD.org> https://wolfram.schneider.org

More information about the freebsd-current mailing list