* [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
[not found] <mailman.926.1604348782.66322.buildroot@busybox.net>
@ 2020-11-03 7:05 ` Andreas Ziegler
2021-09-05 17:25 ` Yann E. MORIN
0 siblings, 1 reply; 4+ messages in thread
From: Andreas Ziegler @ 2020-11-03 7:05 UTC (permalink / raw)
To: buildroot
> Subject: [Buildroot] mkfs.ext4: Could not allocate block in ext2
> filesystem while populating file system
> Message-ID:
> <AM0PR10MB2433AA0D0ED377CB19D8F22A82100@AM0PR10MB2433.EURPRD10.PROD.OUTLOOK.COM>
Hi Kevin,
Check the hint directly below the error message:
> mkfs.ext4: Could not allocate block in ext2 filesystem while
> populating file system
> *** Maybe you need to increase the filesystem size
> (BR2_TARGET_ROOTFS_EXT2_SIZE)
Your new root filesystem is larger than the default space in the image,
which is specified in the buildroot config.
Regards,
Andreas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
2020-11-03 7:05 ` [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system Andreas Ziegler
@ 2021-09-05 17:25 ` Yann E. MORIN
0 siblings, 0 replies; 4+ messages in thread
From: Yann E. MORIN @ 2021-09-05 17:25 UTC (permalink / raw)
To: Andreas Ziegler, kevin.tomary; +Cc: buildroot
Kevin, Andreas, All,
On 2020-11-03 08:05 +0100, Andreas Ziegler spake thusly:
> >Subject: [Buildroot] mkfs.ext4: Could not allocate block in ext2
> > filesystem while populating file system
> >Message-ID:
> > <AM0PR10MB2433AA0D0ED377CB19D8F22A82100@AM0PR10MB2433.EURPRD10.PROD.OUTLOOK.COM>
> Check the hint directly below the error message:
> >mkfs.ext4: Could not allocate block in ext2 filesystem while
> >populating file system
> >*** Maybe you need to increase the filesystem size
> >(BR2_TARGET_ROOTFS_EXT2_SIZE)
>
> Your new root filesystem is larger than the default space in the image,
> which is specified in the buildroot config.
In fact, I believe this is a regression in e2fsprogs 1.46.3; see bug
#14196: https://bugs.busybox.net/show_bug.cgi?id=14196
I'll soon send a patch to fix that both in master and in the stable
2021.08.x branches.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
2020-11-02 17:10 Kevin Tomary
@ 2020-11-02 21:34 ` Peter Seiderer
0 siblings, 0 replies; 4+ messages in thread
From: Peter Seiderer @ 2020-11-02 21:34 UTC (permalink / raw)
To: buildroot
Hello Kevin,
On Mon, 2 Nov 2020 17:10:38 +0000, Kevin Tomary <kevin.tomary@hotmail.com> wrote:
> Hi Evryone
>
> I got the following error after the build of the image. With less packages I didn?t get make errors like these.
> I wanted to include WiFi and Bluetooth according to this blog but the make failed after a long period of building
>
> https://tewarid.github.io/2014/10/10/wireless-on-raspberry-pi-with-buildroot.html
> https://tewarid.github.io/2014/10/29/bluetooth-on-raspberry-pi-with-buildroot.html
>
>
>
>
>
> >>> Generating filesystem image rootfs.ext2
> mkdir -p /home/mehdi/buildroot/output/images
> rm -rf /home/mehdi/buildroot/output/build/buildroot-fs/ext2
> mkdir -p /home/mehdi/buildroot/output/build/buildroot-fs/ext2
> rsync -auH --exclude=/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM /home/mehdi/buildroot/output/target/ /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target
> echo '#!/bin/sh' > /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> echo "set -e" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> echo "chown -h -R 0:0 /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> PATH="/home/mehdi/buildroot/output/host/bin:/home/mehdi/buildroot/output/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" /home/mehdi/buildroot/support/scripts/mkusers /home/mehdi/buildroot/output/build/buildroot-fs/full_users_table.txt /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> echo "/home/mehdi/buildroot/output/host/bin/makedevs -d /home/mehdi/buildroot/output/build/buildroot-fs/full_devices_table.txt /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> printf ' \n' >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> printf ' rm -f /home/mehdi/buildroot/output/images/rootfs.ext2\n /home/mehdi/buildroot/output/host/sbin/mkfs.ext4 -d /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target -r 1 -N 0 -m 5 -L "" -O ^64bit /home/mehdi/buildroot/output/images/rootfs.ext2 "120M" || { ret=$?; echo "*** Maybe you need to increase the filesystem size (BR2_TARGET_ROOTFS_EXT2_SIZE)" 1>&2; exit $ret; }\n' >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> chmod a+x /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> PATH="/home/mehdi/buildroot/output/host/bin:/home/mehdi/buildroot/output/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" FAKEROOTDONTTRYCHOWN=1 /home/mehdi/buildroot/output/host/bin/fakeroot -- /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
> rootdir=/home/mehdi/buildroot/output/build/buildroot-fs/ext2/target
> table='/home/mehdi/buildroot/output/build/buildroot-fs/full_devices_table.txt'
> mke2fs 1.44.5 (15-Dec-2018)
> Creating regular file /home/mehdi/buildroot/output/images/rootfs.ext2
> 64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
> Creating filesystem with 122880 1k blocks and 30720 inodes
> Filesystem UUID: 1990b9bd-d682-4181-b757-d2a3c2153ba5
> Superblock backups stored on blocks:
> 8193, 24577, 40961, 57345, 73729
>
> Allocating group tables: done
> Writing inode tables: done
> Creating journal (4096 blocks): done
> Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "nmap-os-db"
> mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
> *** Maybe you need to increase the filesystem size (BR2_TARGET_ROOTFS_EXT2_SIZE)
> fs/ext2/ext2.mk:46: recipe for target '/home/mehdi/buildroot/output/images/rootfs.ext2' failed
> make: *** [/home/mehdi/buildroot/output/images/rootfs.ext2] Error 1
>
Just increase the filesystem size ('BR2_TARGET_ROOTFS_EXT2_SIZE' in your .config file or
with 'make menuconfig' --> 'Filesystem images' --> 'exact size'), the default from
the defconfigs is adjusted for the minimal package selection...
Regards,
Peter
>
>
> Kevin
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
@ 2020-11-02 17:10 Kevin Tomary
2020-11-02 21:34 ` Peter Seiderer
0 siblings, 1 reply; 4+ messages in thread
From: Kevin Tomary @ 2020-11-02 17:10 UTC (permalink / raw)
To: buildroot
Hi Evryone
I got the following error after the build of the image. With less packages I didn?t get make errors like these.
I wanted to include WiFi and Bluetooth according to this blog but the make failed after a long period of building
https://tewarid.github.io/2014/10/10/wireless-on-raspberry-pi-with-buildroot.html
https://tewarid.github.io/2014/10/29/bluetooth-on-raspberry-pi-with-buildroot.html
>>> Generating filesystem image rootfs.ext2
mkdir -p /home/mehdi/buildroot/output/images
rm -rf /home/mehdi/buildroot/output/build/buildroot-fs/ext2
mkdir -p /home/mehdi/buildroot/output/build/buildroot-fs/ext2
rsync -auH --exclude=/THIS_IS_NOT_YOUR_ROOT_FILESYSTEM /home/mehdi/buildroot/output/target/ /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target
echo '#!/bin/sh' > /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
echo "set -e" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
echo "chown -h -R 0:0 /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
PATH="/home/mehdi/buildroot/output/host/bin:/home/mehdi/buildroot/output/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" /home/mehdi/buildroot/support/scripts/mkusers /home/mehdi/buildroot/output/build/buildroot-fs/full_users_table.txt /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
echo "/home/mehdi/buildroot/output/host/bin/makedevs -d /home/mehdi/buildroot/output/build/buildroot-fs/full_devices_table.txt /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target" >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
printf ' \n' >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
printf ' rm -f /home/mehdi/buildroot/output/images/rootfs.ext2\n /home/mehdi/buildroot/output/host/sbin/mkfs.ext4 -d /home/mehdi/buildroot/output/build/buildroot-fs/ext2/target -r 1 -N 0 -m 5 -L "" -O ^64bit /home/mehdi/buildroot/output/images/rootfs.ext2 "120M" || { ret=$?; echo "*** Maybe you need to increase the filesystem size (BR2_TARGET_ROOTFS_EXT2_SIZE)" 1>&2; exit $ret; }\n' >> /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
chmod a+x /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
PATH="/home/mehdi/buildroot/output/host/bin:/home/mehdi/buildroot/output/host/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" FAKEROOTDONTTRYCHOWN=1 /home/mehdi/buildroot/output/host/bin/fakeroot -- /home/mehdi/buildroot/output/build/buildroot-fs/ext2/fakeroot
rootdir=/home/mehdi/buildroot/output/build/buildroot-fs/ext2/target
table='/home/mehdi/buildroot/output/build/buildroot-fs/full_devices_table.txt'
mke2fs 1.44.5 (15-Dec-2018)
Creating regular file /home/mehdi/buildroot/output/images/rootfs.ext2
64-bit filesystem support is not enabled. The larger fields afforded by this feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 122880 1k blocks and 30720 inodes
Filesystem UUID: 1990b9bd-d682-4181-b757-d2a3c2153ba5
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Copying files into the device: __populate_fs: Could not allocate block in ext2 filesystem while writing file "nmap-os-db"
mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system
*** Maybe you need to increase the filesystem size (BR2_TARGET_ROOTFS_EXT2_SIZE)
fs/ext2/ext2.mk:46: recipe for target '/home/mehdi/buildroot/output/images/rootfs.ext2' failed
make: *** [/home/mehdi/buildroot/output/images/rootfs.ext2] Error 1
Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20201102/88484dc3/attachment.html>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-09-05 17:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.926.1604348782.66322.buildroot@busybox.net>
2020-11-03 7:05 ` [Buildroot] mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system Andreas Ziegler
2021-09-05 17:25 ` Yann E. MORIN
2020-11-02 17:10 Kevin Tomary
2020-11-02 21:34 ` Peter Seiderer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.