From: Mark Wielaard <mark@klomp.org>
To: "Dan Horák" <dhorak@redhat.com>
Cc: buildbot@sourceware.org
Subject: Re: fedora-ppc64le builder out of disk space
Date: Fri, 22 Jul 2022 18:53:56 +0200 [thread overview]
Message-ID: <20220722165356.GC27274@gnu.wildebeest.org> (raw)
In-Reply-To: <20220722164455.e99ffc781f4a9492ecf20697@redhat.com>
Hi Dan,
On Fri, Jul 22, 2022 at 04:44:55PM +0200, Dan Horák wrote:
> On Thu, 21 Jul 2022 21:05:14 +0200
> Mark Wielaard <mark@klomp.org> wrote:
> > The fedora-ppc64le builder at brno ran out of disk space. We are
> > currently use ~30 GB. 5GB of ccache. And 25GB for projects:
> >
> > 4.2M debugedit-fedora-ppc64le
> > 15M bzip2-fedora-ppc64le
> > 37M dwz-fedora-ppc64le
> > 183M elfutils-fedora-ppc64le
> > 596M valgrind-fedora-ppc64le
> > 1.2G libabigail-try-fedora-ppc64le
> > 1.7G gdb-try-fedora-ppc64le
> > 1.7G glibc-fedora-ppc64le
> > 1.8G gdb-fedora-ppc64le
> > 1.9G libabigail-fedora-ppc64le
> > 2.1G binutils-try-fedora-ppc64le
> > 2.2G binutils-fedora-ppc64le
> > 4.7G gccrust-fedora-ppc64le
> > 6.8G gcc-fedora-ppc64le
> >
> > Should we remove some projects, or can the disk space be increased?
>
> I will add more disk space to the VM on Monday, adding an item to my
> to-do list :-)
Thanks. Note that thanks to Frank's idea of running make clean at the
end of each build we saved 8GB+ disk space on the machine. So there is
no immediate urgency anymore.
Cheers,
Mark
next prev parent reply other threads:[~2022-07-22 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:05 Mark Wielaard
2022-07-22 14:44 ` Dan Horák
2022-07-22 16:53 ` Mark Wielaard [this message]
2022-07-25 7:25 ` Dan Horák
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220722165356.GC27274@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=dhorak@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).