Date: Sun, 17 Jul 2022 08:01:21 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 265254] lang/gcc11: build gets stuck Message-ID: <bug-265254-29464-on6cjdvg4I@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265254-29464@https.bugs.freebsd.org/bugzilla/> References: <bug-265254-29464@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=3D265254 --- Comment #22 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Matthias Andree from comment #21) Filling up disks: just rust uses 17+ GiBytes of temporary disk space when tmpfs is largely avoided. Otherwise RAM+SWAP ends up covering that 17+ GiBy= tes. I set up my environments for building such that having 10 or 20 or more examples of such builders going at once would not wipe out the free space intended for use. I avoid configurations that try to cover such via tmpfs use. And, yes, it is not uncommon for me to end up with 4+ compiler toolchains building at once. Note: For UFS, I consider most of the free space as available for use. But, for ZFS, I try to always keep 25%+ free at all times, per the notes in the book The Design and Implementation of the FeeBSD Operating Stystem 2nd Ed. about ZFS performance characteristics (based on its design). --=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-265254-29464-on6cjdvg4I>