Description

On some machine, the root test testMakeFileSystem (https://github.com/containerd/containerd/blob/main/snapshots/devmapper/pool_device_test.go#L240) fails with error

Not enough space to build proposed filesystem while setting up superblock

The reason behind is not a containerd bug itself, but the minimal size of a disk required for a partition is larger than the size of the disk created by the test. Current disk size is approximately 100KB and 200KB https://github.com/containerd/containerd/blob/main/snapshots/devmapper/pool_device_test.go#L43). 1MB and 2MB will be enough.
To reproduce manually, create a disk of size indicated, and try mkfs.ext4 <disk>.
Another workaround is to precise explicitly the blocksize with -b 1024. So, mkfs.ext4 <disk of 100KB> -b 1024 is OK.

Reproduced on two machines:

uname -a
Linux rdr-runtimes-dev-etienne-guesnet-cont-test-1 5.4.0-99-generic #112-Ubuntu SMP Wed Feb 2 17:12:06 UTC 2022 ppc64le ppc64le ppc64le GNU/Linux

and

uname -a
Linux pwr-rt-bionic-x1.fyre.ibm.com 5.4.0-91-generic #102-Ubuntu SMP Fri Nov 5 16:31:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the issue

No response

Describe the results you received and expected

Results:
Not enough space to build proposed filesystem while setting up superblock

Expected:
Nothing (if run in testsuite), or something like

Creating filesystem with 96 1k blocks and 16 inodes

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

using directly mkfs.ext4 in a terminal.

What version of containerd are you using?

main branch of git repository

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response