If you try to use e2fsck from e2fsprogs 1.46.5 or earlier to check a filesystem created with e2fsprogs 1.47.0, it fails:
May 25 14:08:46 fedora systemd-fsck[566]: /dev/vda2 has unsupported feature(s): FEATURE_C12
May 25 14:08:46 fedora systemd-fsck[566]: e2fsck: Get a newer version of e2fsck!
May 25 14:08:46 fedora systemd-fsck[566]: /dev/vda2: ********** WARNING: Filesystem still has errors **********
May 25 14:08:46 fedora systemd-fsck[564]: fsck failed with exit status 12.
this seems to be caused by the new orphan_file feature being enabled by default in 1.47.0. So far, this has caused issues for Debian and Fedora.
This issue is specifically about the very sudden cut-off here. If the description was e.g. "e2fsprogs 1.42.0 and earlier cannot fsck filesystems created with 1.47.0", I'd be less inclined to file a bug. I'm not sure if the sudden transition was intended, but it feels a bit odd. I would kinda have expected that the new feature would be supported-but-not-enabled for a few releases, so that when it was enabled by default, the last few versions could still fsck filesystems created with it. Is this not how e2fsprogs does things?
If you try to use
e2fsckfrom e2fsprogs 1.46.5 or earlier to check a filesystem created with e2fsprogs 1.47.0, it fails:this seems to be caused by the new
orphan_filefeature being enabled by default in 1.47.0. So far, this has caused issues for Debian and Fedora.This issue is specifically about the very sudden cut-off here. If the description was e.g. "e2fsprogs 1.42.0 and earlier cannot fsck filesystems created with 1.47.0", I'd be less inclined to file a bug. I'm not sure if the sudden transition was intended, but it feels a bit odd. I would kinda have expected that the new feature would be supported-but-not-enabled for a few releases, so that when it was enabled by default, the last few versions could still fsck filesystems created with it. Is this not how e2fsprogs does things?