On Wed, 9 Aug 2023 at 13:01, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
This is the upstream change.
The mke2fs program (via the mke2fs.conf file) now enables the metadata_csum_seed and orphan_file features by default.
Yeah, I get that. What I find rather unintuitive and potentially problematic for some more people, is that the exact previous version (in tumbleweed) of fsck, fails with the same flags. Here is what it says, on a block device I made with the newer mkfs flags: hostA:~ # fsck.ext4 /dev/system/test-blk e2fsck 1.46.5 (30-Dec-2021) /dev/system/test-blk has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer version of e2fsck! With the updated package, of course it works hostB:~ # fsck.ext4 /dev/system/test-blk e2fsck 1.47.0 (5-Feb-2023) /dev/system/test-blk: clean, 12/16384 files, 9545/65536 blocks I would have hoped that fsck would at least maybe for one or two major releases, would already learn about new flags before they become enabled for mkfs. But obviously that's not the case. A suggestion for tumbleweed, maybe, for the future, would be to leave out new flags in the /etc/mke2fs.conf file for one or two such (e2fsprogs) release cycles, to smooth the transition. For my own setup, I guess that's what I will do with some "sed -i" reverting the change for a year or so... best regards Patrick