From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4j5pYg71z2z30LN for ; Fri, 16 Oct 2026 15:21:11 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR1" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4j5pYc3yPkz2xHd for ; Fri, 16 Oct 2026 15:21:08 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4j5pYZ23ZSz3B0 for ; Fri, 16 Oct 2026 15:21:06 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1792164066; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9il7E0t/C+poi/5EOQhmnDNeFfwOnGzeRBaEGcm7Rs8=; b=eU0VXTJ/h02216dnJzUfbHKlGmGNuHiYiNV1i8fJe+vuA0rDuNhNgETw+tmnteHDK/gF3D 0uKUSKBonUj+/9Cg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1792164066; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9il7E0t/C+poi/5EOQhmnDNeFfwOnGzeRBaEGcm7Rs8=; b=YVaIQh8z32t/d5d9ayLD9W6RLlcAHRd5UAeUDuyYFKQ1oYU44dlmz31cBPB75WHNCSPIJp lpstH6kGRwW81HQu6udVGVX67vNc5vPnNL5zT0n6p74k+FcwqpuvpSzt9d3Z1ws75HTAg5 LkeGVaFwkd4VwCqOEBPdU4lRCBLghEpyhO7ah9+8BYwMYNAgKgU0WUVHdq15fBb/QWMUeA tYAXEtGHD1rqT9ZuMTJ5CfmLvuGhTy2E+W9wz9vEfjAKGbqfgTSBi3poAc1FUqXwTsy0ze W8Pi7YPY149ntptu6lypWyL4RXFT79F4g4p698hJVpGj9p0H6/Q90C5y8C0N0g== Message-ID: <66862b78-e55f-4e6c-babb-d2e6a147b355@ipfire.org> Date: Fri, 16 Oct 2026 17:21:03 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: Not enough space when building flash-images with new linux-firmware in build From: Adolf Belka To: "IPFire: Development-List" References: <77cd15b8-79be-447b-b11b-4cb126974edc@ipfire.org> Content-Language: en-GB In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi All, So the flash-images built without any problem but then the core-updates section failed with no space left on device. Just to be sure I just checked my desktop machine to make sure it had not filled up any of my partitions but it doesn't look like it. df -hl Filesystem Size Used Avail Use% Mounted on dev 16G 0 16G 0% /dev run 16G 1.6M 16G 1% /run /dev/mapper/hyperion2-root 30G 20G 8.7G 70% / tmpfs 16G 0 16G 0% /dev/shm none 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs 16G 40K 16G 1% /tmp /dev/sdc1 916G 470G 400G 55% /mnt/sdc1 /dev/mapper/hyperion2-boot 289M 58M 216M 22% /boot /dev/mapper/hyperion2-var 15G 8.1G 5.9G 58% /var /dev/mapper/hyperion2-home 408G 310G 78G 80% /home /dev/sdb2 548M 192K 548M 1% /efi tmpfs 3.1G 76K 3.1G 1% /run/user/1000 Here is the error message from the core-updates build. I have not copied all of the core-updates log as it has over 5000 lines. Most of them are the creation of links for the firmware files. So the logs starts near the end of those links when there is the message about no space left. lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0xD.bin -> ti/audio/tas2783/15E2-1-0xD.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0xC.bin -> ti/audio/tas2783/15E2-1-0xC.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0xB.bin -> ti/audio/tas2783/15E2-1-0xB.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0xA.bin -> ti/audio/tas2783/15E2-1-0xA.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0x9.bin -> ti/audio/tas2783/15E2-1-0x9.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-1-0x8.bin -> ti/audio/tas2783/15E2-1-0x8.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xF.bin -> ti/audio/tas2783/15E2-0-0xF.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xE.bin -> ti/audio/tas2783/15E2-0-0xE.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xD.bin -> ti/audio/tas2783/15E2-0-0xD.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xC.bin -> ti/audio/tas2783/15E2-0-0xC.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xB.bin -> ti/audio/tas2783/15E2-0-0xB.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0xA.bin -> ti/audio/tas2783/15E2-0-0xA.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0x9.bin -> ti/audio/tas2783/15E2-0-0x9.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/15E2-0-0x8.bin -> ti/audio/tas2783/15E2-0-0x8.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/1534-2-0xB.bin -> ti/audio/tas2783/1534-2-0xB.bin lrwxrwxrwx root/root 0 2026-10-16 13:33 lib/firmware/1534-2-0x8.bin -> ti/audio/tas2783/1534-2-0x8.bin drwxr-xr-x root/root 0 2026-10-16 14:13 etc/ -rw-r--r-- root/root 89 2026-10-16 14:09 etc/system-release -rw-r--r-- root/root 219 2026-10-16 12:15 etc/os-release -rw-r--r-- root/root 85 2026-10-16 12:15 etc/issue xz: (stdout): Write error: No space left on device tar: Child returned status 1 tar: Error is not recoverable: exiting now make: *** [core-updates:58: install] Error 2 make: Leaving directory '/usr/src/lfs' Let me know if I need to provide other parts or the whole log section, which I can then upload to IPFire nopaste if it is required. Regards, Adolf. On 16/10/2026 14:07, Adolf Belka wrote: > Hi All, > > I have just noticed that there has been a lot of changes to the build process, including around the flash-images section. > > So I am going to run a build with the latest next git status and see how the linux-firmware works with that. > > No point investigating problems in a process that has been changed. > > Regards, > > Adolf. > > On 16/10/2026 13:24, Adolf Belka wrote: >> Hi All, >> >> I have run into a problem when running a build with a new linux-firmware version. After doing the rootfile update and modifications it successfully did the cdrom build step but then in the flash-images build it failed with not enough space and then all subsequent steps failed due to directories or files not being present due to not being able to create the directories with mkdir. >> >> The following is the log output taken up to the first few messages about cannot mkdir - not enough space left on device. >> >> It looks like the very large linux-firmware update is exceeding the available space in the flash-images build loop device. >> >> >> >> Oct 14 18:32:07: Building flash-images make: Entering directory '/home/ahb/sandbox/ipfire-2-builder2/lfs' >> make: Nothing to be done for 'download'. >> make: Leaving directory '/home/ahb/sandbox/ipfire-2-builder2/lfs' >> make: Entering directory '/usr/src/lfs' >> make: Nothing to be done for 'b2'. >> rm -rf /tmp/image.img /tmp/harddisk && mkdir -p /tmp/harddisk >> # Allocate image on disk >> dd if=/dev/zero of=/tmp/image.img bs=512 count=0 seek=$(( 8192 + 1040384 + 65536  + 5242880 )) >> 0+0 records in >> 0+0 records out >> 0 bytes copied, 1.1752e-05 s, 0.0 kB/s >> losetup /dev/loop1 /tmp/image.img >> # Write Partition table >> echo -e "8192,1040384,L,*\n1048576,65536 ,U\n1114112,5242880,L\n" | sfdisk -uS /dev/loop1 >> Checking that no-one is using this disk right now ... OK >> >> Disk /dev/loop1: 3.03 GiB, 3254779904 bytes, 6356992 sectors >> Units: sectors of 1 * 512 = 512 bytes >> Sector size (logical/physical): 512 bytes / 512 bytes >> I/O size (minimum/optimal): 512 bytes / 512 bytes >> >>>>> Created a new DOS (MBR) disklabel with disk identifier 0xf25def00. >> /dev/loop1p1: Created a new partition 1 of type 'Linux' and of size 508 MiB. >> /dev/loop1p2: Created a new partition 2 of type 'EFI (FAT-12/16/32)' and of size 32 MiB. >> /dev/loop1p3: Created a new partition 3 of type 'Linux' and of size 2.5 GiB. >> /dev/loop1p4: Done. >> >> New situation: >> Disklabel type: dos >> Disk identifier: 0xf25def00 >> >> Device       Boot   Start     End Sectors Size Id Type >> /dev/loop1p1 *       8192 1048575 1040384 508M 83 Linux >> /dev/loop1p2      1048576 1114111   65536  32M ef EFI (FAT-12/16/32) >> /dev/loop1p3      1114112 6356991 5242880 2.5G 83 Linux >> >> The partition table has been altered. >> Calling ioctl() to re-read partition table. >> Re-reading the partition table failed.: Invalid argument >> The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or partx(8). >> Syncing disks. >> kpartx -v -a /dev/loop1 >> add map loop1p1 (252:8): 0 1040384 linear 7:1 8192 >> add map loop1p2 (252:9): 0 65536 linear 7:1 1048576 >> add map loop1p3 (252:10): 0 5242880 linear 7:1 1114112 >> # kpartx trigger a automount on some desktop enviroments >> # this leads in failing zerofree after build and umount the image >> # with the sleep 1 prevent this because the image has no fs yet. >> sleep 1 >> # Format them >> mkfs.ext2 -F /dev/mapper/loop1p1 >> mke2fs 1.47.4 (6-Mar-2025) >> Discarding device blocks:      0/520192             done >> Creating filesystem with 520192 1k blocks and 130048 inodes >> Filesystem UUID: d527d8f0-d99e-4a38-a0ea-f23e468823b1 >> Superblock backups stored on blocks: >>      8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409 >> >> Allocating group tables:  0/64     done >> Writing inode tables:  0/64     done >> Writing superblocks and filesystem accounting information:  0/64     done >> >> mkfs.vfat /dev/mapper/loop1p2 >> mkfs.fat 4.2 (2021-01-31) >> mkfs.ext4 -F /dev/mapper/loop1p3 >> mke2fs 1.47.4 (6-Mar-2025) >> Discarding device blocks:      0/655360             done >> Creating filesystem with 655360 4k blocks and 163840 inodes >> Filesystem UUID: 472cb45d-66c9-40f6-9d37-86282522bffd >> Superblock backups stored on blocks: >>      32768, 98304, 163840, 229376, 294912 >> >> Allocating group tables:  0/20     done >> Writing inode tables:  0/20     done >> Creating journal (16384 blocks): done >> Writing superblocks and filesystem accounting information:  0/20     done >> >> # Most systems that use Flashimages has no RTC at boot >> # so the interval check should disables >> tune2fs -i0 /dev/mapper/loop1p3 >> tune2fs 1.47.4 (6-Mar-2025) >> Setting interval between checks to 0 seconds >> # Mount root partition >> mount /dev/mapper/loop1p3 /tmp/harddisk >> # Mount boot partition >> mkdir -pv /tmp/harddisk/boot >> mkdir: created directory '/tmp/harddisk/boot' >> mount /dev/mapper/loop1p1 /tmp/harddisk/boot >> mkdir -pv /tmp/harddisk/boot/efi >> mkdir: created directory '/tmp/harddisk/boot/efi' >> mount /dev/mapper/loop1p2 /tmp/harddisk/boot/efi >> # Copy all files >> # Copy all files from /usr/src/config/rootfiles/common to /tmp/harddisk () >> #  = rootfile to write out >> #  = exclude >> ROOTFILE_PLACEHOLDERS="@BUILDTARGET@=x86_64-pc-linux-gnu @RUST_PLATFORM@=x86_64-unknown-linux-gnu @KERNEL_RELEASE@=6.18.54-ipfire @ARCH@=x86_64 @ARCH_DASHED@=x86-64" /usr/src/src/scripts/archive.files x86_64 /usr/src/config/rootfiles/common  | tee  | tar --create --format=pax --acls --xattrs --xattrs-include='*' --sparse --directory=/ --exclude="dev/pts/*" --exclude="proc/*" --exclude="tmp/*" --exclude="__pycache__"  --files-from=- | tar --extract --format=pax --acls --xattrs --xattrs-include='*' --sparse --directory=/tmp/harddisk >> tar: usr/lib/pkcs11/p11-kit-client.so: Wrote only 512 of 10240 bytes >> tar: usr/lib/pkcs11/p11-kit-trust.so: Wrote only 4096 of 6656 bytes >> tar: usr/lib/pppd: Cannot mkdir: No space left on device >> tar: usr/lib/pppd: Cannot mkdir: No space left on device >> tar: usr/lib/pppd/2.5.2: Cannot mkdir: No such file or directory >> tar: usr/lib/pppd/2.5.2: Cannot mkdir: No such file or directory >> tar: usr/lib/pppd/2.5.2/radattr.so: Cannot open: No such file or directory >> tar: usr/lib/pppd/2.5.2: Cannot mkdir: No such file or directory >> >> Regards, >> >> Adolf. >