cannot generate release for tokay (qpr1) due to disk quota

pupalupalupa

__populate_fs: Disk quota exceeded while writing file "Settings.apk"
e2fsdroid: Disk quota exceeded while populating file system
Out of space? Out of inodes? The tree size of /tmp/targetfiles-k1wf4695/SYSTEM_EXT is 538921984 bytes (513 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 609595392 bytes (581 MB), out of a total partition size of 609595392 bytes (581 MB).
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/tujh/docker/grapheneos/workspace/grapheneos-16-qpr1/releases/2025112200/release-tokay-2025112200/bin/sign_target_files_apks/__main__.py", line 52, in <module>
  File "/home/tujh/docker/grapheneos/workspace/grapheneos-16-qpr1/releases/2025112200/release-tokay-2025112200/bin/sign_target_files_apks/__main__.py", line 46, in _soong_main
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "sign_target_files_apks.py", line 1859, in <module>
  File "sign_target_files_apks.py", line 1852, in main
  File "add_img_to_target_files.py", line 1248, in main
  File "add_img_to_target_files.py", line 1057, in AddImagesToTargetFiles
  File "add_img_to_target_files.py", line 1040, in add_partition
  File "add_img_to_target_files.py", line 383, in AddSystemExt
  File "add_img_to_target_files.py", line 601, in CreateImage
  File "build_image.py", line 581, in BuildImage
  File "build_image.py", line 447, in BuildImageMkfs
  File "common.py", line 328, in RunAndCheckOutput
common.ExternalError: Failed to run command '['mkuserimg_mke2fs', '/tmp/targetfiles-k1wf4695/SYSTEM_EXT', '/tmp/targetfiles-k1wf4695/IMAGES/system_ext.img', 'ext4', 'system_ext', '609595392', '-j', '0', '-T', '1230768000', '-C', '/tmp/targetfiles-k1wf4695/META/system_ext_filesystem_config.txt', '-B', '/tmp/targetfiles-k1wf4695/IMAGES/system_ext.map', '-L', 'system_ext', '-i', '390', '-M', '0', '-U', '5fe9f318-1ea3-53b0-8453-2545d5a554c3', '-S', '7336e06b-9967-5f3c-9888-f621ac12a2c9', '-c', '--inode_size', '256', '/tmp/targetfiles-k1wf4695/META/file_contexts.bin']' (exit code 4):
03:06:45 mkuserimg_mke2fs.py INFO: Env: {'MKE2FS_CONFIG': '/tmp/tmpxl2jlkoy', 'E2FSPROGS_FAKE_TIME': '1230768000'}
03:06:45 mkuserimg_mke2fs.py INFO: Running: /home/tujh/docker/grapheneos/workspace/grapheneos-16-qpr1/releases/2025112200/release-tokay-2025112200/bin/mke2fs -O ^has_journal -L system_ext -N 390 -I 256 -M /system_ext -m 0 -U 5fe9f318-1ea3-53b0-8453-2545d5a554c3 -E hash_seed=7336e06b-9967-5f3c-9888-f621ac12a2c9 -t ext4 -b 4096 /tmp/targetfiles-k1wf4695/IMAGES/system_ext.img 148827
03:06:45 mkuserimg_mke2fs.py INFO: Env: {'E2FSPROGS_FAKE_TIME': '1230768000'}
03:06:45 mkuserimg_mke2fs.py INFO: Running: /home/tujh/docker/grapheneos/workspace/grapheneos-16-qpr1/releases/2025112200/release-tokay-2025112200/bin/e2fsdroid -e -T 1230768000 -C /tmp/targetfiles-k1wf4695/META/system_ext_filesystem_config.txt -B /tmp/targetfiles-k1wf4695/IMAGES/system_ext.map -s -S /tmp/targetfiles-k1wf4695/META/file_contexts.bin -f /tmp/targetfiles-k1wf4695/SYSTEM_EXT -a /system_ext /tmp/targetfiles-k1wf4695/IMAGES/system_ext.img
03:06:45 mkuserimg_mke2fs.py ERROR: Failed to run e2fsdroid_cmd: __populate_fs: Disk quota exceeded while writing file "Settings.apk"
e2fsdroid: Disk quota exceeded while populating file system

mke2fs 1.47.2 (1-Jan-2025)
Creating filesystem with 148827 4k blocks and 400 inodes
Filesystem UUID: 5fe9f318-1ea3-53b0-8453-2545d5a554c3
Superblock backups stored on blocks: 
	32768, 98304

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


__populate_fs: Disk quota exceeded while writing file "Settings.apk"
e2fsdroid: Disk quota exceeded while populating file system

Guess there is a system.img space quota problem (maybe m3 design has so much better resources that does not fit 513 MB heheh)

P.S. building out of docker (archlinux native host build), do not try to guess its docker due to folder location

de0u

pupalupalupa Is this an unmodified build (e.g., no extra apps are being included in the build)?

pupalupalupa

de0u yep, i just synced it with repo (about 4-5 hours ago) and built with official wiki. There is no changes in code by me

pupalupalupa

Also it was clean-build, so i also done vendor-files with adevtool generate-all -d tokay

(dont know if it ships to system.img, but...)

pupalupalupa

and i also have about 2.8T space available on disk (but i guess by error it yells at space while generating system.img which was limited by specific size like ENV-variable or smth else). And my /home is btrfs (dont know if it is important or not)

/dev/mapper/arch-home 3.6T 889G 2.8T 25% /home

pupalupalupa

I got error on script/generate-release.sh tokay 2025112200

So the build compiled successfully, OTA was also created successfully, but I can't generate a release
(also will OTA update succeed if the new system.img content partition size is small???)

de0u

pupalupalupa I got error on script/generate-release.sh tokay 2025112200

I just built 025112100 for bluejay and tokay, all the way through generate-release.sh without incident.

I did notice that during the process more than 10 GB of space was consumed in /tmp (more for tokay than for bluejay, I think).

Meanwhile, the log messages from the code that builds the file system images talk about computing the needed size for each image.

Overall, I did not encounter an error building a signed release image for tokay, and I suspect your /tmp ran out of space.

de0u

pupalupalupa Also will OTA update succeed if the new system.img content partition size is small???

If image generation threw an error and stopped, I would not regard anything associated with that event as trustworthy. I would probably nuke both out and releases and start over.