Open cooljimy84 opened 4 months ago
after changing https://github.com/OpenVoiceOS/ovos-buildroot/blob/24a7b5beb1ceb5eb1753446ecc9c03ee05bf2c53/buildroot-external/scripts/post-build.sh#L99 to 20GB, this get me to my next out of space issue.
mke2fs 1.46.5 (30-Dec-2021)
INFO: ext4(overlayfs.ext4): cmd: "e2fsck -pvfD '/home/builder/ovos-buildroot/buildroot/output/images/overlayfs.ext4'" (stderr):
INFO: hdimage(disk.img): adding partition 'esp' (in MBR) from 'esp.vfat' ...
INFO: hdimage(disk.img): adding partition 'rootfs-1' (in MBR) from 'rootfs.squashfs' ...
INFO: hdimage(disk.img): adding partition 'rootfs-2' (in MBR) from 'rootfs.squashfs' ...
INFO: hdimage(disk.img): adding partition 'overlayfs' (in MBR) from 'overlayfs.ext4' ...
INFO: hdimage(disk.img): adding partition 'homefs' (in MBR) from 'homefs.ext4' ...
ERROR: hdimage(disk.img): write 4096 bytes: No space left on device
ERROR: hdimage(disk.img): failed to write image partition 'homefs'
INFO: hdimage(disk.img): cmd: "rm -f "/home/builder/ovos-buildroot/buildroot/output/images/disk.img"" (stderr):
ERROR: hdimage(disk.img): failed to generate disk.img
Error during image generation.
Cleaning up temporary files.
make[1]: *** [Makefile:816: target-post-image] Error 1
make[1]: Leaving directory '/home/builder/ovos-buildroot/buildroot'
rsync -ah --progress buildroot/output/images/disk.img release/OpenVoiceOS_rpi3_64_20240222_1416.img
sending incremental file list
rsync: [sender] link_stat "/home/builder/ovos-buildroot/buildroot/output/images/disk.img" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.2.7]
make: *** [Makefile:26: rpi3_64] Error 23
You are using teh VFS driver on your system instead of the overlayfs.
I am currently working on building host podman/skopeo/jq tools to account for this. As a possible quickfix you could create/add the below file in the directory of your build host system
~/.config/containers/storage.conf
I'll hold off making a pull request for the image creation "homefs.ext4" size as just making it 20GB is kinda over kill (and it seems to shrink it down to the sized used after it's finished copying) Unless you want me to test and possibly change the other build options pi4, x86 and find a size that currently works ?
Towards the end of the make rpi3_64 command I get hit with this, I have plenty of disk space, just the loop back image seems full.
I can try expanding the image and running make again (not savy enough to know if it would pick up from where it was)