Date: Fri, 19 Oct 2018 15:51:19 +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-UCAWrRWs1H@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 #11 from Sylvain Garrigues <sylvain@sylvaingarrigues.com> --- (In reply to Glen Barber from comment #10) I agree it is not a bug per se, but rather a comment on the commit which increased the size of all VMs by 10GB (50% increase) per Kirk=E2=80=99s req= uest who noticed free space was getting low on a 20GB disk for actual people who do = want to download the full source history and recompile both world and kernel and want to keep some kernel and cannot or don=E2=80=99t want to mess with grow= fs (that=E2=80=99s a bunch of conditions) Kirk admits he doesn=E2=80=99t need the full 30GB (anything >25GB seems fin= e) and I believe 27GB for instance is plenty enough while still allowing to use defa= ult disk settings of 30GB (which happens when you click on `Launch this [FreeBS= D] image=E2=80=99) - and in addition anything under 30GB is free if you use a = low resource Google Cloud machine. So my comment/request on your commit, if you wish to honor it, is =E2=80=98= can you solve Kirk=E2=80=99s problem with VMSIZE=3D27GB instead of the 30GB you cho= se, or even better maybe can you make introduce VMSIZE-GCE or VMSIZE-CLOUDWARE =3D 10GB= for instance so that cloud images we upload to Amazon, Google and Azure are sma= ller and adapted to the size of the disk they are installed onto since growfs *d= oes* its job there?=E2=80=99 --=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-UCAWrRWs1H>