Hi,

as I haven't found discussion by searching, I thought I bring up a gotcha I ran into today, on a host recently updated to tumbleweed 20230801 level.

With a somewhat recent update to e2fsprogs, now at 1.47.0 compared to May '23 at 1.46.5, the set of mkfs flags has changed:

--- /root/mke2fs.conf.20230512 2023-08-09 12:00:14.379476597 +0200
+++ /etc/mke2fs.conf 2023-06-14 19:20:22.000000000 +0200
@@ -14 +14 @@
- features = has_journal,extent,huge_file,flex_bg,metadata_csum,64bit,dir_nlink,extra_isize
+ features = has_journal,extent,huge_file,flex_bg,metadata_csum,metadata_csum_seed,64bit,dir_nlink,extra_isize,orphan_file

For me, this resulted in an otherwise fine virtual machine with 20230512 userlevel, not booting after an "rsync copy migration" into a fresh root filesystem mkfs'ed with these new flags. Reason being that 3 months older fsck - the sytemd boot time rootfs service actually - goes "failed".

I guess I'll need just use flag override options going forward, to cope with that, but thought I'd bring it to attention here at least.

best regards

  Patrick