Description of problem: I have a notebook with Ubuntu 16.04 installed. I wanted to try Fedora 25 in a dual-boot configuration. My Ubuntu 16.04 installation had two filesystems: / which was ext4 /home which was ext3 When I tried to boot Ubuntu 16.04 again after having installed and used Fedora 25 a bit, it turned out that Ubuntu couldn't boot anymore. It turned out that my filesystems had been upgraded to ext4 and with features which were not supported by the e2fsprogs version included with Ubuntu. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install an older system which uses ext3 (or ext4 with fewer features than Fedora 25 support) 2. Install Fedora 25 on a separate partition 3. Try to boot the older system Actual results: The filesystems of the older system have been upgraded which breaks the older system. Expected results: Fedora should not perform unexpected filesystem upgrades. Either ask or at least warn a user before this happens. Additional info: In the case of Ubuntu 16.04, I could get the system working again by editing /etc/fstab, changing ext3 to ext4 for the mount on /home and by installing a backported version of the newer e2fsprogs.
Hi, thanks for the report, however this has nothing to do with e2fsprogs but rather anaconda (Fedora installer) that might have done something unexpected maybe. Not sure what happened there. Changing component to anaconda. -Lukas
Nothing should be intentionally "upgrading" other filesystems on the disk during install; I don't think that's likely what's happening. When you say: > It turned out that my filesystems had been upgraded to ext4 and with features which were not supported by the e2fsprogs version included with Ubuntu. what evidence did you find? Kernel messages about unsupported features? which features? Do you have logs?
e2fsck in Ubuntu gave me an error that multiple features the filesystem was using were not supported, so it couldn't check the filesystem. These turned out to be ext4 features. The filesystem was also listed in /etc/fstab with ext3 before, which prevented it from being mounted. I don't know if Fedora keeps any logs of its installation around. Maybe Fedora upgrades a disk when during the installation when an existing ext3 filesystem is picked as ext4, do not format.
(In reply to Julius Schwartzenberg from comment #3) > > I don't know if Fedora keeps any logs of its installation around. Post-install, logs should be located in /var/log/anaconda/
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.