Control: severity -1 important Control: retitle -1 e2fsprogs generates filesystems which cannot be mounted on systems with older e2fsprogs
It turns out for debos the situation is a bit different. Since debos uses packages on the host to prepare the partitions, new features in e2fsprogs from unstable which are unsupported in the target suite causes the built system to not boot. One such failure at boot-time of a Debian testing system is when systemd-fsck tries to check a filesystem, it fails to mount the device: /dev/mmcblk0p5 has unsupported feature(s): FEATURE_C12 So, in short we cannot run images built for suites with older e2fsprogs on a host system which has e2fsprogs >=1.47.0-1. Fixing grub2 will not fix the issue for debos, so I have retitled the bug. In debos with newer e2fsprogs, we can set the following flag on a partition to disable the feature which allows the system running older e2fsprogs to boot, but older e2fsprogs doesn't allow us to set this flag: features: [ "^orphan_file" ] So to my mind, the bug is in e2fsprogs as it doesn't maintain backwards compatibility. I have reduced the severity of the bug since a workaround for debos does exist. I wonder whether the bug should be reassigned to e2fsprogs ?
