configs/raspberrypi3_defconfig: fix filesystem size
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Increase the filesystem size for raspberrypi3 by setting BR2_TARGET_ROOTFS_EXT2_SIZE to "120M". The filesystem for raspberrypi3_64 has the same size.
Fixes:
Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)
configs/raspberrypi3_defconfig +1 -0
@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"
Signature · 1 line
2.7.4
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Leon, All,
On 2018-06-29 12:23 +0300, Leon Anavi spake thusly:
Quoted 7 lines
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
I don't have this issue here:
$ make raspberrypi3_defconfig
$ make
$ du -hs output/target/
57M output/target/
$ ls -lsh output/images/
total 159M
24K -rw-r--r-- 1 ymorin ymorin 24K Jun 30 19:35 bcm2710-rpi-3-b.dtb
28K -rw-r--r-- 1 ymorin ymorin 25K Jun 30 19:35 bcm2710-rpi-3-b-plus.dtb
24K -rw-r--r-- 1 ymorin ymorin 23K Jun 30 19:35 bcm2710-rpi-cm3.dtb
8.0M -rw-r--r-- 1 ymorin ymorin 32M Jun 30 19:35 boot.vfat
54M -rw-r--r-- 1 ymorin ymorin 60M Jun 30 19:35 rootfs.ext2
0 lrwxrwxrwx 1 ymorin ymorin 11 Jun 30 19:35 rootfs.ext4 -> rootfs.ext2
4.0K drwxr-xr-x 3 ymorin ymorin 4.0K Jun 30 19:24 rpi-firmware
93M -rw-r--r-- 1 ymorin ymorin 93M Jun 30 19:35 sdcard.img
4.7M -rw-r--r-- 1 ymorin ymorin 4.7M Jun 30 19:35 zImageRegards,
Yann E. MORIN.
Quoted 24 lines
Signed-off-by Leon Anavi <[email protected]>--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 6 lines
2.7.4 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hi Yann,
Quoted 11 lines · Yann E. MORIN
Leon, All,
On 2018-06-29 12:23 +0300, Leon Anavi spake thusly:
Quoted 7 lines
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file systemI don't have this issue here:
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
I have noticed that the same fix has been already applied to raspberrypi3_64_defconfig. I hope my patch will be merged to prevent this issue in future for raspberrypi3_defconfig.
Thanks,
Leon
Quoted 44 lines
$ make raspberrypi3_defconfig $ make $ du -hs output/target/ 57M output/target/ $ ls -lsh output/images/ total 159M 24K -rw-r--r-- 1 ymorin ymorin 24K Jun 30 19:35 bcm2710-rpi-3-b.dtb 28K -rw-r--r-- 1 ymorin ymorin 25K Jun 30 19:35 bcm2710-rpi-3-b-plus.dtb 24K -rw-r--r-- 1 ymorin ymorin 23K Jun 30 19:35 bcm2710-rpi-cm3.dtb 8.0M -rw-r--r-- 1 ymorin ymorin 32M Jun 30 19:35 boot.vfat 54M -rw-r--r-- 1 ymorin ymorin 60M Jun 30 19:35 rootfs.ext2 0 lrwxrwxrwx 1 ymorin ymorin 11 Jun 30 19:35 rootfs.ext4 -> rootfs.ext2 4.0K drwxr-xr-x 3 ymorin ymorin 4.0K Jun 30 19:24 rpi-firmware 93M -rw-r--r-- 1 ymorin ymorin 93M Jun 30 19:35 sdcard.img 4.7M -rw-r--r-- 1 ymorin ymorin 4.7M Jun 30 19:35 zImageRegards,
Yann E. MORIN.Quoted 24 lines
Signed-off-by Leon Anavi <[email protected]>--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 6 lines
2.7.4 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 3 lines
Leon Anavi Software Engineer konsulko.com
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Leon, All,
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
Quoted 13 lines · Yann E. MORIN
Quoted 11 lines
Leon, All,
On 2018-06-29 12:23 +0300, Leon Anavi spake thusly:
Quoted 7 lines
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file systemI don't have this issue here:
Quoted 8 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
I have noticed that the same fix has been already applied to
raspberrypi3_64_defconfig. I hope my patch will be merged to prevent this issue in future forraspberrypi3_defconfig.
The raspberrypi3_64_defconfig has always had the size set to 120MiB from the onset, because it builds more kernel modules and thus takes more place (at least, according to the commit log (commit 9bbea36e3e).
I am not opposed to the change, BTW.
Regards,
Yann E. MORIN.
Quoted 54 lines
Thanks,
LeonQuoted 44 lines
$ make raspberrypi3_defconfig $ make $ du -hs output/target/ 57M output/target/ $ ls -lsh output/images/ total 159M 24K -rw-r--r-- 1 ymorin ymorin 24K Jun 30 19:35 bcm2710-rpi-3-b.dtb 28K -rw-r--r-- 1 ymorin ymorin 25K Jun 30 19:35 bcm2710-rpi-3-b-plus.dtb 24K -rw-r--r-- 1 ymorin ymorin 23K Jun 30 19:35 bcm2710-rpi-cm3.dtb 8.0M -rw-r--r-- 1 ymorin ymorin 32M Jun 30 19:35 boot.vfat 54M -rw-r--r-- 1 ymorin ymorin 60M Jun 30 19:35 rootfs.ext2 0 lrwxrwxrwx 1 ymorin ymorin 11 Jun 30 19:35 rootfs.ext4 -> rootfs.ext2 4.0K drwxr-xr-x 3 ymorin ymorin 4.0K Jun 30 19:24 rpi-firmware 93M -rw-r--r-- 1 ymorin ymorin 93M Jun 30 19:35 sdcard.img 4.7M -rw-r--r-- 1 ymorin ymorin 4.7M Jun 30 19:35 zImageRegards,
Yann E. MORIN.Quoted 24 lines
Signed-off-by Leon Anavi <[email protected]>--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 6 lines
2.7.4 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildrootSignature · 3 lines
Leon Anavi Software Engineer konsulko.com
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Leon, All,
On 2018-06-30 21:11 +0200, Yann E. MORIN spake thusly:
Quoted 1 line
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
[--SNIP--]
Quoted 4 lines
Quoted 4 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
Could you please provide a bit more details on your buildsystem: what is the filesystem you use to build?
In the past, we had issues when the build was done on zfs for example, because it reports nvalid (POSIX-wise) results about the size for small files, which zfs entirely stores in the inode, thus reporting sero used blocks.
I'm afraid something similar may be happening here...
Regards,
Yann E. MORIN.
Quoted 81 lines
Quoted 3 lines
I have noticed that the same fix has been already applied to
raspberrypi3_64_defconfig. I hope my patch will be merged to prevent this issue in future forraspberrypi3_defconfig.The
raspberrypi3_64_defconfighas always had the size set to 120MiB from the onset, because it builds more kernel modules and thus takes more place (at least, according to the commit log (commit9bbea36e3e).I am not opposed to the change, BTW.
Reviewed-by "Yann E. MORIN" <[email protected]>Regards,
Yann E. MORIN.Quoted 54 lines
Thanks,
LeonQuoted 44 lines
$ make raspberrypi3_defconfig $ make $ du -hs output/target/ 57M output/target/ $ ls -lsh output/images/ total 159M 24K -rw-r--r-- 1 ymorin ymorin 24K Jun 30 19:35 bcm2710-rpi-3-b.dtb 28K -rw-r--r-- 1 ymorin ymorin 25K Jun 30 19:35 bcm2710-rpi-3-b-plus.dtb 24K -rw-r--r-- 1 ymorin ymorin 23K Jun 30 19:35 bcm2710-rpi-cm3.dtb 8.0M -rw-r--r-- 1 ymorin ymorin 32M Jun 30 19:35 boot.vfat 54M -rw-r--r-- 1 ymorin ymorin 60M Jun 30 19:35 rootfs.ext2 0 lrwxrwxrwx 1 ymorin ymorin 11 Jun 30 19:35 rootfs.ext4 -> rootfs.ext2 4.0K drwxr-xr-x 3 ymorin ymorin 4.0K Jun 30 19:24 rpi-firmware 93M -rw-r--r-- 1 ymorin ymorin 93M Jun 30 19:35 sdcard.img 4.7M -rw-r--r-- 1 ymorin ymorin 4.7M Jun 30 19:35 zImageRegards,
Yann E. MORIN.Quoted 24 lines
Signed-off-by Leon Anavi <[email protected]>--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 6 lines
2.7.4 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildrootSignature · 3 lines
Leon Anavi Software Engineer konsulko.comSignature · 10 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hi Yann, All,
Quoted 11 lines · Yann E. MORIN
Leon, All,
On 2018-06-30 21:11 +0200, Yann E. MORIN spake thusly:
Quoted 1 line
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
[--SNIP--]
Quoted 4 lines
Quoted 4 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
Could you please provide a bit more details on your buildsystem: what is the filesystem you use to build?
The filesystem of my build machine is ext4. More details about the Ubuntu version:
Distributor ID:??? Ubuntu
Description:??? Ubuntu 16.04.4 LTS
Release:??? 16.04
Codename:??? xenial
Best regards,
Leon
Quoted 88 lines
In the past, we had issues when the build was done on zfs for example, because it reports nvalid (POSIX-wise) results about the size for small files, which zfs entirely stores in the inode, thus reporting sero used blocks.
I'm afraid something similar may be happening here...
Regards,
Yann E. MORIN.Quoted 77 lines
Quoted 3 lines
I have noticed that the same fix has been already applied to
raspberrypi3_64_defconfig. I hope my patch will be merged to prevent this issue in future forraspberrypi3_defconfig.The
raspberrypi3_64_defconfighas always had the size set to 120MiB from the onset, because it builds more kernel modules and thus takes more place (at least, according to the commit log (commit9bbea36e3e).I am not opposed to the change, BTW.
Reviewed-by "Yann E. MORIN" <[email protected]>Regards,
Yann E. MORIN.Quoted 52 lines
Thanks,
LeonQuoted 43 lines
$ make raspberrypi3_defconfig $ make $ du -hs output/target/ 57M output/target/ $ ls -lsh output/images/ total 159M 24K -rw-r--r-- 1 ymorin ymorin 24K Jun 30 19:35 bcm2710-rpi-3-b.dtb 28K -rw-r--r-- 1 ymorin ymorin 25K Jun 30 19:35 bcm2710-rpi-3-b-plus.dtb 24K -rw-r--r-- 1 ymorin ymorin 23K Jun 30 19:35 bcm2710-rpi-cm3.dtb 8.0M -rw-r--r-- 1 ymorin ymorin 32M Jun 30 19:35 boot.vfat 54M -rw-r--r-- 1 ymorin ymorin 60M Jun 30 19:35 rootfs.ext2 0 lrwxrwxrwx 1 ymorin ymorin 11 Jun 30 19:35 rootfs.ext4 -> rootfs.ext2 4.0K drwxr-xr-x 3 ymorin ymorin 4.0K Jun 30 19:24 rpi-firmware 93M -rw-r--r-- 1 ymorin ymorin 93M Jun 30 19:35 sdcard.img 4.7M -rw-r--r-- 1 ymorin ymorin 4.7M Jun 30 19:35 zImageRegards,
Yann E. MORIN.Quoted 24 lines
Signed-off-by Leon Anavi <[email protected]>--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 6 lines
2.7.4 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildrootSignature · 3 lines
Leon Anavi Software Engineer konsulko.comSignature · 10 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 3 lines
Leon Anavi Software Engineer konsulko.com
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hello,
Quoted 11 lines · Leon Anavi
Quoted 9 lines · Yann E. MORIN
On 2018-06-30 21:11 +0200, Yann E. MORIN spake thusly:
Quoted 1 line
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
[--SNIP--]
Quoted 4 lines
Quoted 4 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
Could you please provide a bit more details on your buildsystem: what is the filesystem you use to build?
Quoted 7 lines
The filesystem of my build machine is ext4. More details about the Ubuntu version:
Distributor ID:??? Ubuntu
Description:??? Ubuntu 16.04.4 LTS
Release:??? 16.04
Codename:??? xenial
I reproduced the error here:
system: Ubuntu 18.04 LTS
filesystem: ext4
commit: 78af2a6362 (the same from the CI build mentioned above) wrapped error message:
Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "busybox"
From the CI url mentioned above it seems the same occurs also in the GitLab runners, so I started a few builds. Note: please trust the log and ignore the job status, all jobs failed when uploading artifacts, probably my mistake in the hacked .gitlab-ci.yml.
2018.05 [1] ok
2018.05 [2] ok
2018.05-140-g8b0fd3cb49 [3] fail
2018.05-240-g43ebb35e9b [4] fail
2018.05-340-g9f26e91cc5 [5] fail
2018.05-440-gc0d19a2083 [6] fail
2018.05-505-g78af2a6362 [7] fail
2018.05-559-g855295b658 [8] fail
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/71910855
[2] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670469
[3] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670740
[4] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671047
[5] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671078
[6] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671235
[7] https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
[8] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670542
Regards,
Ricardo
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Ricardo, All,
On 2018-07-02 00:50 -0300, Ricardo Martincoski spake thusly:
Quoted 20 lines · Leon Anavi
Quoted 11 lines · Yann E. MORIN
Quoted 9 lines
On 2018-06-30 21:11 +0200, Yann E. MORIN spake thusly:
Quoted 1 line
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
[--SNIP--]
Quoted 4 lines
Quoted 4 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
Could you please provide a bit more details on your buildsystem: what is the filesystem you use to build?
Quoted 7 lines
The filesystem of my build machine is ext4. More details about the Ubuntu version:
Distributor ID:??? Ubuntu
Description:??? Ubuntu 16.04.4 LTS
Release:??? 16.04
Codename:??? xenial
Quoted 7 lines
I reproduced the error here:
system: Ubuntu 18.04 LTS
filesystem: ext4
commit:78af2a6362(the same from the CI build mentioned above) wrapped error message:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "busybox"
I also was ultimately able toreproduce on my machine.
What pwuzzles me is that a did a build that was successful. Then I cleaned and did a rebuilt form scratch and it failed. And the failing file is never the same, which leads me to think it depends a lot of the order of files as returned by readdir()...
And in any way, the size is already approaching the limit, so it does make sense to increase it.
Quoted 14 lines
From the CI url mentioned above it seems the same occurs also in the GitLab runners, so I started a few builds. Note: please trust the log and ignore the job status, all jobs failed when uploading artifacts, probably my mistake in the hacked .gitlab-ci.yml.
2018.05 [1] ok
2018.05 [2] ok
2018.05-140-g8b0fd3cb49 [3] fail
2018.05-240-g43ebb35e9b [4] fail
2018.05-340-g9f26e91cc5 [5] fail
2018.05-440-gc0d19a2083 [6] fail
2018.05-505-g78af2a6362 [7] fail
2018.05-559-g855295b658 [8] fail
Quoted 8 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/71910855
[2] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670469
[3] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670740
[4] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671047
[5] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671078
[6] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671235
[7] https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
[8] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670542
OK, so what is weird is that we all noticed different failing files or directories (busybox for Ricardo, shm for me, others for Leon), while the Gitlab-CI runners all failed on nfs_check, whether on Ricardo's or the main Buildroot jobs...
Anyway, as I said; let's increase the size.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hi Yann,
Quoted 60 lines · Yann E. MORIN
Ricardo, All,
On 2018-07-02 00:50 -0300, Ricardo Martincoski spake thusly:
Quoted 18 lines · Leon Anavi
Quoted 10 lines · Yann E. MORIN
Quoted 9 lines
On 2018-06-30 21:11 +0200, Yann E. MORIN spake thusly:
Quoted 1 line
On 2018-06-30 21:03 +0300, Leon Anavi spake thusly:
[--SNIP--]
Quoted 4 lines
Quoted 4 lines
Thank you for the feedback. I have experienced this issue while building branch master on Ubuntu 16.04. As discussed in the IRC channel on Friday the same issue has been reproduced in the CI, Job #78257653 triggered by Thomas Petazzoni: https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
Could you please provide a bit more details on your buildsystem: what is the filesystem you use to build?
Quoted 7 lines
The filesystem of my build machine is ext4. More details about the Ubuntu version:
Distributor ID:??? Ubuntu
Description:??? Ubuntu 16.04.4 LTS
Release:??? 16.04
Codename:??? xenialQuoted 7 lines
I reproduced the error here:
system: Ubuntu 18.04 LTS
filesystem: ext4
commit:78af2a6362(the same from the CI build mentioned above) wrapped error message:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "busybox"I also was ultimately able toreproduce on my machine.
What pwuzzles me is that a did a build that was successful. Then I cleaned and did a rebuilt form scratch and it failed. And the failing file is never the same, which leads me to think it depends a lot of the order of files as returned by
readdir()...And in any way, the size is already approaching the limit, so it does make sense to increase it.
Quoted 14 lines
From the CI url mentioned above it seems the same occurs also in the GitLab runners, so I started a few builds. Note: please trust the log and ignore the job status, all jobs failed when uploading artifacts, probably my mistake in the hacked .gitlab-ci.yml.
2018.05 [1] ok
2018.05 [2] ok
2018.05-140-g8b0fd3cb49 [3] fail
2018.05-240-g43ebb35e9b [4] fail
2018.05-340-g9f26e91cc5 [5] fail
2018.05-440-gc0d19a2083 [6] fail
2018.05-505-g78af2a6362 [7] fail
2018.05-559-g855295b658 [8] failQuoted 8 lines
[1] https://gitlab.com/buildroot.org/buildroot/-/jobs/71910855
[2] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670469
[3] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670740
[4] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671047
[5] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671078
[6] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78671235
[7] https://gitlab.com/buildroot.org/buildroot/-/jobs/78257653
[8] https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/78670542
Quoted 6 lines
OK, so what is weird is that we all noticed different failing files or directories (busybox for Ricardo, shm for me, others for Leon), while the Gitlab-CI runners all failed on
nfs_check, whether on Ricardo's or the main Buildroot jobs...Anyway, as I said; let's increase the size.
Thank you very much for the deep investigation and for sharing the results. I hope that by merging my patch for increasing the size this issue will not affect anyone in future.
Thanks,
Leon
Quoted 4 lines
Regards,
Yann E. MORIN.
Signature · 3 lines
Leon Anavi Software Engineer konsulko.com
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hello,
Quoted 1 line · Leon Anavi
On 2.07.2018 19:17, Yann E. MORIN wrote:
[snip]
Quoted 5 lines
Quoted 1 line
Anyway, as I said; let's increase the size.
Thank you very much for the deep investigation and for sharing the results. I hope that by merging my patch for increasing the size this issue will not affect anyone in future.
Sure. I agree with you both. Let's increase the size.
Regards,
Ricardo
Arnout Vandecappelle
AppliedPATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
In reply to Leon AnaviQuoted 9 lines · Leon Anavi
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file systemSigned-off-by Leon Anavi <[email protected]>
Applied to master, thanks.
It's a pity we didn't get to the bottom of why this error was not happening
every time, or why it didn't happen before. But, as mentioned, the fix is simple and we were close to the limit.
I've extended the commit log a little bit.
Regards,
Arnout
Quoted 17 lines
--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Arnout, All,
On 2018-07-08 00:35 +0200, Arnout Vandecappelle spake thusly:
Quoted 5 lines · Leon Anavi
Quoted 4 lines
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.
Quoted 7 lines
Quoted 5 lines
Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services" mkfs.ext4: Could not allocate block in ext2 filesystem while populating file systemSigned-off-by Leon Anavi <[email protected]>Applied to master, thanks.
Not really, I'm afraid...
Quoted 3 lines
It's a pity we didn't get to the bottom of why this error was not happening
every time, or why it didn't happen before. But, as mentioned, the fix is simple and we were close to the limit.
I did two tests on the same, the first was successfull, the second failed. The only difference being that the machine was unloaded for the first one, while I was doing something else for the second one... Yeah, not very conclusive... :-(
Regards,
Yann E. MORIN.
Quoted 34 lines
I've extended the commit log a little bit.
Regards,
ArnoutQuoted 17 lines
--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"Signature · 10 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Hi Arnout, Yann, All,
Quoted 11 lines · On Sun, Jul 8, 2018, 12:16 Yann E. MORIN <[email protected]> wrote:
Arnout, All,
On 2018-07-08 00:35 +0200, Arnout Vandecappelle spake thusly:
Quoted 7 lines · Leon Anavi
Quoted 6 lines
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.Fixes:
Copying files into the device:__populate_fs: Could not allocate blockin ext2 filesystem while writing file "services"
Quoted 9 lines
Quoted 1 line
Quoted 1 line
mkfs.ext4: Could not allocate block in ext2 filesystem while
populating file system
Quoted 4 lines
Quoted 2 lines
Signed-off-by Leon Anavi <[email protected]>Applied to master, thanks.
Not really, I'm afraid...
I am also afraid that I still don't see it in master.
Best regards, Leon
Quoted 62 lines
Quoted 1 line
It's a pity we didn't get to the bottom of why this error was not
happening
Quoted 1 line
every time, or why it didn't happen before. But, as mentioned, the fix
is simple
Quoted 1 line
and we were close to the limit.
I did two tests on the same, the first was successfull, the second failed. The only difference being that the machine was unloaded for the first one, while I was doing something else for the second one... Yeah, not very conclusive... :-(
Regards,
Yann E. MORIN.Quoted 10 lines
I've extended the commit log a little bit.
Regards,
ArnoutReview
Quoted 5 lines
--- configs/raspberrypi3_defconfig | 1 + 1 file changed, 1 insertion(+)(quoted diff) +0
-0b/configs/raspberrypi3_defconfig
Quoted 20 lines
configs/raspberrypi3_defconfig BR2_PACKAGE_HOST_MTOOLS=y · line 34
Quoted 12 lines
index 856f321..0ef9afe 100644
configs/raspberrypi3_defconfig +1
-0@@ -28,6 +28,7 @@ BR2_PACKAGE_HOST_MTOOLS=y # Filesystem / image BR2_TARGET_ROOTFS_EXT2=y BR2_TARGET_ROOTFS_EXT2_4=y +BR2_TARGET_ROOTFS_EXT2_SIZE="120M" # BR2_TARGET_ROOTFS_TAR is not set BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi3/post-build.sh" BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi3/post-image.sh"--
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDFQuoted 4 lines
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
Quoted 2 lines
'------------------------------^-------^------------------^--------------------'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180708/d14583ab/attachment.html>
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
Quoted 22 lines · Leon Anavi
Hi Arnout, Yann, All,
On Sun, Jul 8, 2018, 12:16 Yann E. MORIN <[email protected] <mailto:[email protected]>> wrote:
Arnout, All,
On 2018-07-08 00:35 +0200, Arnout Vandecappelle spake thusly:
> On 29-06-18 11:23, Leon Anavi wrote:
> > Increase the filesystem size for raspberrypi3 by setting
> >BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem for > >raspberrypi3_64has the same size.
> >
> > Fixes:
> > Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services"
> > mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
> >
> > Signed-off-by: Leon Anavi <[email protected] <mailto:[email protected]>>
>
Quoted 6 lines
>? Applied to master, thanks.
Not really, I'm afraid...
I am also afraid that I still don't see it in master.
I pushed now, thanks for the heads-up.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 1/1 configs/raspberrypi3_defconfig: fix filesystem size
In reply to Leon AnaviQuoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Leon" == Leon Anavi <[email protected]> writes:
Increase the filesystem size for raspberrypi3 by setting
BR2_TARGET_ROOTFS_EXT2_SIZEto "120M". The filesystem forraspberrypi3_64has the same size.
Quoted 6 lines
Fixes:
Copying files into the device:__populate_fs: Could not allocate block in ext2 filesystem while writing file "services"
mkfs.ext4: Could not allocate block in ext2 filesystem while populating file systemSigned-off-by Leon Anavi <[email protected]>
Committed to 2018.02.x and 2018.05.x, thanks.
Signature · 1 line
Bye, Peter Korsgaard