Description of problem: Fresh install of Mageia 3 beta 2. If acl is applied to ext4 (root) partition then reboot after installation fails. Version-Release number of selected component (if applicable): Mageia 3 beta 2 + upgrades during installation (2013-03-09). How reproducible: Just install, partition and check acl for ext4 partition. Steps to Reproduce: 1. During installation make sure that ext4 partition contains acl option 2. Update packages during installation 3. Reproducible: Steps to Reproduce:
I can't confirm is works fine (netinstall or coming beta3). (and as default partition are in ext4 with acl) What do you have for errors ?
Status: NEW => UNCONFIRMEDComponent: Installer => RPM PackagesEver confirmed: 1 => 0
The actual problem seems to be that I had created btrfs partitions and btrfs does not support acl option. Selecting the acl for ext4 / partition puts the same option to all other partitions and therefore causing boot problem.
Some more information now that I managed to boot again. The /etc/fstab does not contain acl in other that ext4 partitions, however dracut complains "acl not supported" during boot while trying to mount btrfs partitions. Maybe dracut tries to make some "intelligent" guesses causing this problem.
If I boot to rescue mode, mount the /, edit /etc/fstab and remove the acl from ext4 partitions then Mageia 3b3 boots just fine.
in bug 9195 you can see that ext4 has acl as default enable, so, did you change something yourself ? again in my test, as default it works fine.
I did not have acl enabled as default (custom partition path).
Version: Cauldron => 3
Hi Jari. We couldn't reproduce your issue and Mageia 3 is not supported anymore. Could you tell us if it's still valid in Mageia 4 and/or Mageia 5 RC?
Keywords: (none) => NEEDINFOCC: (none) => mageiaSource RPM: (none) => dracut
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: UNCONFIRMED => RESOLVEDCC: (none) => nicResolution: (none) => OLD