Out of space? error while building automotive 12 bsp in IMX-8q-evk board

[althafahammed]

I have tried to build for nxp-8q-evk board with lunch (mek_8q_car-userdebug) for Android Automotive 12.0.0_2.1.0 (Linux 5.15.32 BSP)​​ by adding some vendor application but i got out of memory exception in vendor partition

As a solution to this i have changed the BoardConfigCommon.mk all FILE_SYSTEM_TYPE to erofs from ext4 but that time build was successful but kernel is not loading after flashing also we try to increase the vendor partion size from board config and build was successful but that build has some issue while flashing in to the board 

Can you please check the logs and let me know how to proceed further when we encountered such error 

LOGS
-----------------

2025-01-22 14:28:56 - build_image.py - ERROR   : Failed to build out/target/product/mek_8q/vendor.img from out/target/product/mek_8q/vendor
Out of space? Out of inodes? The tree size of out/target/product/mek_8q/vendor is 694234112 bytes (662 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 660418560 bytes (629 MB), out of a total partition size of 671088640 bytes (640 MB).
Traceback (most recent call last):
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/__main__.py", line 12, in <module>
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 174, in _run_module_as_main
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/internal/stdlib/runpy.py", line 72, in _run_code
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/build_image.py", line 943, in <module>
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/build_image.py", line 935, in main
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/build_image.py", line 546, in BuildImage
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/build_image.py", line 378, in BuildImageMkfs
  File "/home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/build_image/common.py", line 312, in RunAndCheckOutput
common.ExternalError: Failed to run command '['mkuserimg_mke2fs', '-s', 'out/target/product/mek_8q/vendor', 'out/target/product/mek_8q/vendor.img', 'ext4', 'vendor', '660418560', '-j', '0', '-D', 'out/ta
rget/product/mek_8q/system', '-L', 'vendor', '-M', '0', '--inode_size', '256', 'out/target/product/mek_8q/obj/ETC/file_contexts.bin_intermediates/file_contexts.bin']' (exit code 4):
14:28:54 mkuserimg_mke2fs.py INFO: Env: {'MKE2FS_CONFIG': '/home/bluejay.sdv@quest-global.com/android_build/out/soong/.temp/tmpdEkMvo'}
14:28:54 mkuserimg_mke2fs.py INFO: Running: /home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/mke2fs -O ^has_journal -L vendor -I 256 -M /vendor -m 0 -E android_sparse -t ext4 -b 40
96 out/target/product/mek_8q/vendor.img 161235
14:28:55 mkuserimg_mke2fs.py INFO: Env: {}
14:28:55 mkuserimg_mke2fs.py INFO: Running: /home/bluejay.sdv@quest-global.com/android_build/out/host/linux-x86/bin/e2fsdroid -p out/target/product/mek_8q/system -S out/target/product/mek_8q/obj/ETC/file
_contexts.bin_intermediates/file_contexts.bin -f out/target/product/mek_8q/vendor -a /vendor out/target/product/mek_8q/vendor.img
14:28:56 mkuserimg_mke2fs.py ERROR: Failed to run e2fsdroid_cmd: __populate_fs: Could not allocate block in ext2 filesystem while writing file "MacawAlexa.apk"
e2fsdroid: Could not allocate block in ext2 filesystem while populating file system

mke2fs 1.45.4 (23-Sep-2019)
Creating filesystem with 161235 4k blocks and 40320 inodes
Filesystem UUID: e060c8a4-448b-4264-ba4b-fbe691631318
Superblock backups stored on blocks: 
  32768, 98304

Allocating group tables: done                            
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

__populate_fs: Could not allocate block in ext2 filesystem while writing file "MacawAlexa.apk"
e2fsdroid: Could not allocate block in ext2 filesystem while populating file system

14:29:11 ninja failed with: exit status 1

[Bio_TICFSL]

Hello,

This usually happens when you've added things to the build which can not fit into the size allocated for one of the partitions (usually system.img or vendor.img). If you have added anything, try removing it, and seeing if the build finishes

Regards

[althafahammed]

Yaa, after removing the apps which i added i could able to build the same

But, I need a solution which help i can able to build with the apps i added

[althafahammed]

When i changed the SYSTEMFILETYPE in the BoardCommonConfig to "erofs" i could able to build but if i make that change kernal is not booting up is there any change i need to do to support the erofs file system