Hide Forgot
Created attachment 493137 [details] Anaconda traceback file Description of problem: During upgrade from Fedora 14 to Fedora 15, anaconda fails to find the btrfs root partition resulting in: AttributeError: 'NoneType' object has no attribute 'path' anaconda 15.27 exception reportTraceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2099, in mkDevRoot dev = "%s/%s" % (instPath, root.path) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1207, in mkDevRoot self.fsset.mkDevRoot() File "/usr/lib64/python2.7/site-packages/pyanaconda/upgrade.py", line 296, in upgradeMountFilesystems anaconda.storage.mkDevRoot() Version-Release number of selected component (if applicable): 15.27 How reproducible: 3/3 on this system. Didn't try a new system image Steps to Reproduce: 1. Install Fedora 14 with Btrfs RAID10 root 2. Try to upgrade to Fedora 15 3. After selecting the Fedora 14 system to upgrade, error will occur and debug console will be an option Actual results: Expected results: Additional info:
How did you install F14 onto a btrfs raid10? The fedora installer does not support any btrfs raid at this time. That means you can only create basic btrfs volumes and cannot use preexisting complex btrfs volumes during installation.
I'll try to come up with repro steps in a fresh VM tonight, because I can't quite remember how I did it. I remember it would let me build the raid10 btrfs, but wouldn't boot into it because dracut doesn't do what it ought. I fixed dracut with a script similar to the one reproduced at http://happy.penguins.tw/?p=142 so I might have just used similar post-install instructions (i.e., btrfs device add ...)
That's probably right (btrfs device add ...). Either way, we haven't developed support for any btrfs raid devices, so you're going to be out of luck until/unless you can present a single basic btrfs volume for us to use.
Is this support on the schedule? Failing that, would you be willing to review patches I write to add it?
(In reply to comment #4) > Is this support on the schedule? Failing that, would you be willing to review > patches I write to add it? We have a placeholder in the anaconda roadmap for it, but no definite plans. If you write patches I can take a look at them. Just make sure you follow the methodology used for all other devices. That is: - use udev rules where possible to gather information about the devices - don't run any commands that put everything together magically (we need to be able to see what the device structure should be so we can tell whether or not things are in order) - a command to activate/assemble a single device is okay, but a command to assemble them all is not Some people are already working on improving the information provided by blkid and udev for complex btrfs devices like raid level, snapshot source, &c. That should appear in rawhide within the next couple of days or weeks.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping