| Summary: | Mageia 8 cannot mount a Mageia 9 ext4 partition due to the latter having a feature not supported by the former. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Nicolas Nicolas <joe_c_moi> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, mrmazda, yvesbrungard |
| Version: | Cauldron | Keywords: | IN_ERRATA8, IN_ERRATA9 |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://www.mageialinux-online.org/forum/topic-30462-1+demarrage-mageia-8-hs.php | ||
| Whiteboard: | |||
| Source RPM: | e2fsprogs-1.47.0-1.mga9 | CVE: | |
| Status comment: | |||
|
Description
Nicolas Nicolas
2023-03-05 17:25:45 CET
Nicolas Nicolas
2023-03-05 17:26:26 CET
Summary:
Adding a Mageia 9 Beta 1 in an Mageia 8 fstab break startup of Mageia 8 =>
Adding a Mageia 9 Beta 1 partition in ext4 format in an Mageia 8 fstab break startup of Mageia 8 Thank you for this instructive report, which makes it appear that we need to update Mageia 8 e2fsprogs as you nicely demonstrate. e2fsprogs has various committers, so assigning this bug globally. Assignee:
bugsquad =>
pkg-bugs We are not going to push 1.47 to mga8
papoteur
2023-03-06 07:54:43 CET
CC:
(none) =>
yves.brungard_mageia @tmb: a couple words on why not would be nice For an example on why it would be good: for existing portable Mageia 8 systems, i.e persistent Live, to access various disks on host. (at least until mga9 ships, so not a strong point) Better point may be when using portable media formatted on systems using C12 CC:
(none) =>
fri Per Comment 2: closing as wontfix. If minds change: reopen and edit errata. Resolution:
(none) =>
WONTFIX Also affects fsarchiver, bug 28791. To note in Mageia 8 Errata and also somewhere regarding live - because they may be used as backup tools. (mention mounting, e2fsck, and fsarchiver) Whiteboard:
IN_ERRATA9 =>
(none) The default file /etc/mke2fs.conf encloses:
ext4 = {
features = has_journal,extent,huge_file,flex_bg,metadata_csum,metadata_csum_seed,64bit,dir_nlink,extra_isize,orphan_file
Could we remove the new default options metadata_csum_seed and orphan_file features ?
It seems that Debian has done it. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622 (In reply to Morgan Leijström from comment #5) > To note in Mageia 8 Errata and also somewhere regarding live - because they > may be used as backup tools. (mention mounting, e2fsck, and fsarchiver) https://wiki.mageia.org/en/Persistent_live_systems#Ext4_option_difference
Felix Miata
2023-06-17 23:18:10 CEST
CC:
(none) =>
mrmazda Hello, I have pushed a release in testing where these options metadata_csum_seed and orphan_file are removed. e2fsprogs-1.47.0-2.mga9
papoteur
2023-06-18 18:07:56 CEST
Source RPM:
e2fsprogs...mga8 =>
e2fsprogs-1.47.0-1.mga9 So new installs using next ISOs (or any netinstall) will be compatible with Mga8 but systems fresh installed from beta2 and earlier netinstalls will have formatted partitions with the C12 feature? (I may misunderstand something, this is not my cup of tea) Currently in errata as https://wiki.mageia.org/en/Mageia_9_Errata#ext4_format_uses_feature_C12_which_are_not_recognized_by_older_fsck (and mentioned in errata 8 and per comment 9) I guess we need a wide agreement on this before eventual pushing Updated erratas |