On Sat, Jul 04, 2026 at 07:27:29PM +0200, Cyril Brulebois wrote: > root@iot-isobuilder-52:~# fallocate -l 1G foo.img > root@iot-isobuilder-52:~# kpartx -asv foo.img
Why kpartx and not losetup -P? kpartx uses device mapper, while losetup -P uses the internal partition support of the kernel. > The foo.img file doesn't exist in the first place, it is not getting > partitioned, and yet, we have both loop0p1 and loop0p2 coming up, with > sizes that match the system image built previously. Another hint is that > we have 259:0 and 259:1 as MAJ:MIN, instead of 253:0 and 253:1 when the > system image was being worked on. So the devices switch between possibly device-mapper (dynamically allocated) and blkext (fixed 259). > Looking at the changes between v6.12.90 and v6.12.94, the following one > seems pretty plausible: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3cef9aa17bf7dac59095b6972454c049a5fe97c0 The problem: this is about loop, you use device-mapper via kpartx. Does this also happen with a current kernel? Bastian -- Another Armenia, Belgium ... the weak innocents who always seem to be located on a natural invasion route. -- Kirk, "Errand of Mercy", stardate 3198.4
