I’ve seen this issue discussed but cannot find if it has been fixed in mender (convert or client). I mender converted a Debian image and the resulting root partition has an incorrect filesystem size. The disk info shows 8.3G root partitions, yet filesystem usage lists the active one as only 2.4G. Interestingly, the /data partition looks good:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 119.1G 0 disk ├─mmcblk0p1 179:1 0 44M 0 part /uboot ├─mmcblk0p2 179:2 0 8.3G 0 part / ├─mmcblk0p3 179:3 0 8.3G 0 part └─mmcblk0p4 179:4 0 102.5G 0 part /data
Filesystem Size Used Avail Use% Mounted on /dev/root 2.4G 1.7G 571M 75% / devtmpfs 460M 0 460M 0% /dev tmpfs 464M 0 464M 0% /dev/shm tmpfs 464M 12M 452M 3% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 464M 0 464M 0% /sys/fs/cgroup /dev/mmcblk0p4 101G 73M 96G 1% /data /dev/mmcblk0p1 43M 18M 25M 42% /uboot tmpfs 93M 0 93M 0% /run/user/1000
I did the conversion using mender-convert version 076f5e3, and my mender-client on the image is 3.0.0. Unfortunately I am limited to this version of the client, as my OS is Debian Stretch and it does not have dependencies that the newer client requires.
I know I can do a resize2fs to fix the mismatch, but would much prefer that mender create an image with matching partition and filesystem sizes. Has a solution been implemented for this issue? Or maybe there are mender-convert settings that could solve it? I’m concerned that even after fixing the active root partition with a resize2fs, a subsequent switch over to the passive partition would show the same problem.