arm64 kernel builds fails due to insufficient disk space

Asked by Frank Heimes

Just recently arm64 kernel builds started to fail due to insufficient disk space:
E: Build killed with signal TERM after 150 minutes of inactivity
Build needed 13:17:20, no disk space

I think it started when add. kernel flavors or even RT was added.)

An obvious workaround is of course to disable some of the builds (like special kernels and/or the generation of dbgsym) - however, I think it would be great if a standard kernel build succeeds again for arm64 (with 'standard' I mean: just take the Canonical kernel teams kernel sources and just rebuild them as they are in a PPA).

I got conformation from the kernel team that this happens for (at least Andrea) as well if he builds in a private PPA; but it does not happen in the kernel team PPAs (like bootstrap or unstable), but we believe that these have none-standard resources ...

Is it possible to increase the disk space? (maybe even the default disk space)
Should this be transferred into a LP bug rather than a question?

Thx, Frank

Question information

English Edit question
Ubuntu Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :

What is the output of:

lsb_release -a; uname -a; df -h


Revision history for this message
Frank Heimes (fheimes) said :

Sorry, I don't know - and I don't know a way to get that information out of a PPA build environment.
The must be a default disk space size for PPAs, no?

Revision history for this message
actionparsnip (andrew-woodhead666) said :

Open a terminal, or if you are using CLI only then just run the command
Then copy the output and paste it as an update on your question

Revision history for this message
Manfred Hampl (m-hampl) said (last edit ):

In my opinion there is some misinterpretation.

1. I do not see a disk space problem in the output, but a "timeout exceeded" issue.

The text "no disk space" indeed is strange.
It seems to me that the reporting of disk space used during build nowadays is broken, compare

2. If the problem is related to the Launchpad Build farm, then this question has been asked in the wrong area (Ubuntu) and should be relocated to the question area for Launchpad itself.

I suggest to reassign this question document to "Launchpad itself" or eventually creating a new one on that area.
Hopefully the Launchpad builder admins can help.

For the misleading "no disk space" message someone might create a bug report, also against "Launchpad itself" after checking to make sure that such bug report does not already exist.

Revision history for this message
Manfred Hampl (m-hampl) said :

Related question in "Launchpad itself":

Can you help with this problem?

Provide an answer of your own, or ask Frank Heimes for more information if necessary.

To post a message you must log in.