Description of problem: btrfs RAID1 volumes do not get assembled throwing the "open_ctree failed" message in the dmesg log when mounting them using the volume UUID or the first from total two used device names until the "btrfs device scan" command is entered. As the mentioned command isn't called automatically during the boot sequence, mounting of the volume via corresponding fstab entry fails too. The following links point to the same problem experienced in case of different linux distributions: https://features.opensuse.org/313130 http://www.spinics.net/lists/linux-btrfs/msg02902.html Please, fix initscripts to call "/sbin/btrfs device scan" prior to mounting volumes via fstab. Version-Release number of selected component (if applicable): initscripts-9.34-20.mga2 How reproducible: always Steps to Reproduce (example for sda4 and sdb4): 1. Create btrfs RAID1 volume # mkfs.btrfs -m raid1 -d raid1 /dev/sda4 /dev/sdb4 2. Create a new mountpoint # mkdir /mnt/whatever 3. Use blkid to identify the btrfs RAID1 volume # blkid 4. Define the volume in the fstab UUID=01234567-89ab-cdef-0123-456789abcdef /mnt/whatever btrfs relatime 0 0 5. Reboot # reboot 6. Check if the device gets mounted ...
I just tested that with fresh MGA2 installation and got a different behavior. It throws me into the emergency mode and surprisingly manual mounting from there works ...
This feature seems to be taken over by systemd .... changing the component ...
Source RPM: initscripts-9.34-20.mga2.src.rpm => systemd-44-13.mga2.src.rpm
URL: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=851275
Colin, the bug reporter suspects systemd, but maybe a different package is the culprit here? Can you help me find out which one?
Keywords: (none) => TriagedCC: (none) => mageia, stormi
Keywords: Triaged => (none)
Hi Samuel. If you look at the URL pointing to the Fedora bug, you can see it's been resolved in the systemd component. You can find a lot more info there. Regards, Jaromir.
Indeed, thanks. This is definitely for our systemd maintainer then :) To Colin: the fedora bug contains useful information.
Keywords: (none) => TriagedAssignee: bugsquad => mageia
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD