The issue here is that in LP: #1817097 e2fsprogs was changed to use 4k blocks by default regardless of the created fs size. Changing the command to force a 1012 byte blocksize causes the mkfs.ext2 command to succeed:
$ dd if=/dev/zero of=/tmp/image.ext3 bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.00136542 s, 60.0 MB/s $ mkfs.ext2 -F -m 0 -N 10 /tmp/image.ext3 mke2fs 1.45.1 (12-May-2019) /tmp/image.ext3: Not enough space to build proposed filesystem while setting up superblock $ mkfs.ext2 -F -m 0 -N 10 -b 1024 /tmp/image.ext3 mke2fs 1.45.1 (12-May-2019) Discarding device blocks: done Creating filesystem with 80 1k blocks and 16 inodes Allocating group tables: done Writing inode tables: done Writing superblocks and filesystem accounting information: done There are two ways to solve this: 1) change the command to force 1024 byte block sizes; the -b argument has existed in e2fsprogs since at least the 1.42 version included in ubuntu 12.04 LTS. 2) the image was setup to be laughably small to ensure the testsuite could run successfully in relatively small scale environments; we could bump the generated image to 128 blocks (512KB), which would let mkfs succeed while still not excessively consuming space. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834192 Title: apparmor mult_mount regression test fails in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1834192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
