I want my image to be at least 10 GB in size, so I use PUMP 10G. However, the resulting image is only 3.7 GB in size. The problem is, that you are using dd to increase the image, where you are setting the parameter bs=${1}. But the bs parameter is limited in size, e.g., 2 GB.
### PUMP 10G
0+1 records in
0+1 records out
2147479552 bytes (2.1 GB, 2.0 GiB) copied, 30.6786 s, 70.0 MB/s
Model: (file)
Disk /root/Base.img: 3951MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 4194kB 49.2MB 45.0MB primary fat32 lba
2 50.3MB 1804MB 1753MB primary ext4
add map loop9p1 (253:18): 0 87851 linear 7:9 8192
add map loop9p2 (253:19): 0 7618552 linear 7:9 98304
rootfs: 39794/107072 files (0.1% non-contiguous), 239385/428032 blocks
resize2fs 1.46.2 (28-Feb-2021)
Resizing the filesystem on /dev/mapper/loop9p2 to 952319 (4k) blocks.
The filesystem on /dev/mapper/loop9p2 is now 952319 (4k) blocks long.
del devmap : loop9p2
del devmap : loop9p1
add map loop9p1 (253:18): 0 87851 linear 7:9 8192
add map loop9p2 (253:19): 0 7618552 linear 7:9 98304
update-binfmts: warning: qemu-arm already enabled in kernel.
update-binfmts: warning: qemu-armeb already enabled in kernel.
update-binfmts: warning: qemu-aarch64 already enabled in kernel.
I want my image to be at least 10 GB in size, so I use
PUMP 10G. However, the resulting image is only 3.7 GB in size. The problem is, that you are using dd to increase the image, where you are setting the parameterbs=${1}. But thebsparameter is limited in size, e.g., 2 GB.