Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Oct 2018 07:10:13 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 232313] GCE image size is now > 30 GB, above free quota
Message-ID:  <bug-232313-227-314i6F0BXX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-232313-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-232313-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232313

--- Comment #5 from Sylvain Garrigues <sylvain@sylvaingarrigues.com> ---
(In reply to Kirk McKusick from comment #4)

Well I am using the GCE machines for the exact same thing: I am building ar=
m64
kernels and worlds, I am packaging with them (`make packages`) and I am also
making snapshots of them. I have a few months history, keeping old worlds a=
nd
images.

And yet, on the 30GB GCE machine, I have more than 10GB free space left:

[root@dev ~]# df -h
Filesystem         Size    Used   Avail Capacity  Mounted on
/dev/gpt/rootfs     28G     15G     11G    59%    /
devfs              1.0K    1.0K      0B   100%    /dev

[root@dev ~]# du -hs /usr/src/ /usr/obj
3.2G    /usr/src/
4.7G    /usr/obj

[root@dev ~]# gpart show da0
=3D>       3  62914549  da0  GPT  (30G)
         3        32    1  freebsd-boot  (16K)
        35   2097152    2  freebsd-swap  (1.0G)
   2097187  60817365    3  freebsd-ufs  (29G)

Granted, there are some big parts (like ZFS and bhyve) that I am not buildi=
ng:
[root@dev ~]# cat /etc/src.conf=20=20
MALLOC_PRODUCTION=3DYES
WITH_CCACHE_BUILD=3DYES
WITHOUT_TESTS=3DYES
WITHOUT_BHYVE=3DYES
WITHOUT_PROFILE=3DYES
WITHOUT_ZFS=3DYES
WITHOUT_DEBUG_FILES=3DYES

I am not sure if it would fill up the 11GB of free space (I do take your wo=
rd
on it) but yet your use case (build world and kernel in a bhyve machine)
doesn't seem compatible with mine (having Google Cloud machines running Fre=
eBSD
for free, like it used to be before gcj committed the change).

I see three solutions:
1/ keep the root partition to a more reasonable size and make growfs and bh=
yve
work together (the cleanest solution)
2/ reduce temporarily the size by a few GB (maybe losing 2GB is enough, my
making VMSIZE=3D28GB) so that anybody can try and install the GCE images on
Google Cloud.=20=20
3/ have special treatment for cloud images... most other Unix images are ar=
ound
10GB, why is FreeBSD 32GB, like a Microsoft Windows image?

>From https://console.cloud.google.com/compute/images:

debian-9-tf-nightly-v20181017   10 Go   Debian=20=20
coreos-stable-1855-4-0-v20180911        9 Go    CoreOS=20=20
centos-7-v20181011      10 Go   CentOS
rhel-7-v20181011        10 Go RedHat
sles-15-v20180816       10 Go   SUSE Linux Enterprise
ubuntu-1804-bionic-v20181003    10 Go   Canonical
windows-server-1803-dc-core-v20181009   32 Go   Microsoft=20=20=20=20=20=20=
=20

FreeBSD ? 32GB.

Glen, what do you think?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232313-227-314i6F0BXX>