| Message ID | 20211106181424.299041-1-peron.clem@gmail.com |
|---|---|
| State | Superseded |
| Headers | show |
| Series | [1/2] configs/beelink_gs1: increase rootfs size to 120M | expand |
Hi Clément, On 06/11/21 19:14, Clément Péron wrote: > For the moment Beelink GS1 use a default rootfs size of 60M > which make sometimes the build failed due to missing space. > > Increase the rootfs size to 120M. > > Signed-off-by: Clément Péron <peron.clem@gmail.com> Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Hi Clément, On 06/11/2021 19:14, Clément Péron wrote: > For the moment Beelink GS1 use a default rootfs size of 60M > which make sometimes the build failed due to missing space. That's surprising... The only thing in the rootfs is busybox, so the rootfs size should be way less than 1MB, let alone 60MB... Also, "sometimes" is suspicious. The rootfs should be almost binary identical between two builds (there are some dates and paths in there if you don't enable BR2_REPRODUCIBLE). Do you have a bit more detail/example of how it fails? Regards, Arnout > > Increase the rootfs size to 120M. > > Signed-off-by: Clément Péron <peron.clem@gmail.com> > --- > configs/beelink_gs1_defconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/configs/beelink_gs1_defconfig b/configs/beelink_gs1_defconfig > index e88f3e3b69..1872aabdf0 100644 > --- a/configs/beelink_gs1_defconfig > +++ b/configs/beelink_gs1_defconfig > @@ -24,6 +24,7 @@ BR2_PACKAGE_AUTOSSH=y > BR2_PACKAGE_DROPBEAR=y > BR2_TARGET_ROOTFS_EXT2=y > BR2_TARGET_ROOTFS_EXT2_4=y > +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" > > # Firmware > BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
Hi Arnout, On Tue, 25 Jan 2022 at 21:57, Arnout Vandecappelle <arnout@mind.be> wrote: > > Hi Clément, > > On 06/11/2021 19:14, Clément Péron wrote: > > For the moment Beelink GS1 use a default rootfs size of 60M > > which make sometimes the build failed due to missing space. > > That's surprising... The only thing in the rootfs is busybox, so the rootfs > size should be way less than 1MB, let alone 60MB... > > Also, "sometimes" is suspicious. The rootfs should be almost binary identical > between two builds (there are some dates and paths in there if you don't enable > BR2_REPRODUCIBLE). > > Do you have a bit more detail/example of how it fails? Agree, "Sometimes" is not the proper word, I received two times a mail saying missing space in the target, maybe it was due to a package that was wrongly added by default with some dependencies? (Can't find them again). Anyway 60MiB is really low and I need to change it every time I want to add a graphic stack. I will edit the commit log and send a V2. Regards, Clement > > Regards, > Arnout > > > > > Increase the rootfs size to 120M. > > > > Signed-off-by: Clément Péron <peron.clem@gmail.com> > > --- > > configs/beelink_gs1_defconfig | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/configs/beelink_gs1_defconfig b/configs/beelink_gs1_defconfig > > index e88f3e3b69..1872aabdf0 100644 > > --- a/configs/beelink_gs1_defconfig > > +++ b/configs/beelink_gs1_defconfig > > @@ -24,6 +24,7 @@ BR2_PACKAGE_AUTOSSH=y > > BR2_PACKAGE_DROPBEAR=y > > BR2_TARGET_ROOTFS_EXT2=y > > BR2_TARGET_ROOTFS_EXT2_4=y > > +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" > > > > # Firmware > > BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
diff --git a/configs/beelink_gs1_defconfig b/configs/beelink_gs1_defconfig index e88f3e3b69..1872aabdf0 100644 --- a/configs/beelink_gs1_defconfig +++ b/configs/beelink_gs1_defconfig @@ -24,6 +24,7 @@ BR2_PACKAGE_AUTOSSH=y BR2_PACKAGE_DROPBEAR=y BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # Firmware BR2_TARGET_ARM_TRUSTED_FIRMWARE=y
For the moment Beelink GS1 use a default rootfs size of 60M which make sometimes the build failed due to missing space. Increase the rootfs size to 120M. Signed-off-by: Clément Péron <peron.clem@gmail.com> --- configs/beelink_gs1_defconfig | 1 + 1 file changed, 1 insertion(+)