Build package error - 'No space left on device' on lcy01-amd64-021

Asked by Andy Lavr on 2018-10-28

Hi!

Build package error - 'No space left on device'

Why not enough space? A few days ago the build was successful ...

Full log:

https://code.launchpad.net/~wip-kernel/+archive/ubuntu/ppa/+build/15579930

https://launchpadlibrarian.net/395082938/buildlog_ubuntu-cosmic-amd64.linux_4.19.0-041900.201810221809.wipg2_BUILDING.txt.gz

CC kernel/time/timer.o
  CC [M] mm/hwpoison-inject.o
  CC arch/x86/kernel/tsc_msr.o
  CC arch/x86/kernel/io_delay.o
  CC [M] mm/z3fold.o
  CC arch/x86/kernel/rtc.o
{standard input}: Assembler messages:
{standard input}: Fatal error: can't write 17 bytes to section .text of arch/x86/kernel/rtc.o: 'No space left on device'
/<<PKGBUILDDIR>>/arch/x86/kernel/rtc.c:207:1: fatal error: closing dependency file arch/x86/kernel/.rtc.o.d: No space left on device
 device_initcall(add_rtc_cmos);
 ^~~~~~~~~~~~~~~
compilation terminated.
{standard input}: Fatal error: can't close arch/x86/kernel/rtc.o: No space left on device
make[4]: *** [/<<PKGBUILDDIR>>/scripts/Makefile.build:305: arch/x86/kernel/rtc.o] Error 1
make[3]: *** [/<<PKGBUILDDIR>>/scripts/Makefile.build:546: arch/x86/kernel] Error 2
make[2]: *** [/<<PKGBUILDDIR>>/Makefile:1052: arch/x86] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC kernel/time/hrtimer.o
  CC [M] fs/btrfs/transaction.o
{standard input}: Assembler messages:
{standard input}: Fatal error: can't write 13 bytes to section .text of mm/z3fold.o: 'No space left on device'
{standard input}: Fatal error: can't close mm/z3fold.o: No space left on device
make[3]: *** [/<<PKGBUILDDIR>>/scripts/Makefile.build:312: mm/z3fold.o] Error 1
make[2]: *** [/<<PKGBUILDDIR>>/Makefile:1052: mm] Error 2
  CC [M] fs/btrfs/inode.o
/<<PKGBUILDDIR>>/fs/btrfs/disk-io.c:4531:1: fatal error: closing dependency file fs/btrfs/.disk-io.o.d: No space left on device
 };

Best regards, Andy.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
2018-10-28
Last query:
2018-10-28
Last reply:
2018-10-28
Best Colin Watson (cjwatson) said : #1

Every build runs in a fresh VM image with the exact same amount of disk, and this hasn't changed for a couple of years. If a build is running out of space when it wasn't previously, then something must have changed in your build or in one of its build-dependencies; I suggest diffing the build log against the last successful build log and looking for differences there (though I imagine you'll need to filter out some noise due to parallel building).

Andy Lavr (lavrandy) said : #2

Thanks Colin Watson, that solved my question.