libreport version: 2.0.8 cmdline: /usr/bin/python /sbin/anaconda --graphical --selinux --repo cdrom:///dev/sr0:/mnt/install/source executable: /sbin/anaconda exnFileName: /tmp/anaconda-tb-xJvPop hashmarkername: anaconda kernel: 3.3.0-0.rc3.git7.2.fc17.x86_64 other involved packages: product: Fedora reason: NameError: global name 'BTRFSError' is not defined release: Cannot get release name. time: Wed 22 Feb 2012 02:51:53 AM UTC version: 17-Alpha anaconda-tb-xJvPop: Binary file, 558709 bytes description: :The following was filed automatically by anaconda: :anaconda 17.11 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devices.py", line 4035, in listSubVolumes : except BTRFSError as e: : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1587, in handleBTRFSFormat : for subvol_dict in btrfs_dev.listSubVolumes(): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1713, in handleUdevDeviceFormat : self.handleBTRFSFormat(info, device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1077, in addUdevDevice : self.handleUdevDeviceFormat(info, device) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 2006, in _populate : self.addUdevDevice(dev) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1896, in populate : self._populate(progressWindow) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 473, in reset : cleanupOnly=cleanupOnly) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 102, in storageInitialize : storage.reset() : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch : self.dir = self.steps[self.step].target(self.anaconda) : File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 247, in go_forward : self.dispatch() : File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1200, in nextClicked : self.anaconda.dispatch.go_forward() :NameError: global name 'BTRFSError' is not defined environ: :LC_NUMERIC=C :LANGKEY=en :LVM_SUPPRESS_FD_WARNINGS=1 :initrd=initrd.img :GCONF_GLOBAL_LOCKS=1 :PATH=/tmp/product:/tmp/updates:/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin :PIXMAPPATH=/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/ :HOME=/tmp :DISPLAY=:1 :LANG=en_US.UTF-8 :TERM=linux :XAUTHORITY=/root/.Xauthority :GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/ :SHLVL=0 :LIBUSER_CONF=/tmp/libuser.2wTET0 :LD_LIBRARY_PATH=/tmp/product:/tmp/updates :GNOME_DISABLE_CRASH_DIALOG=1 :PYTHONPATH=/tmp/product:/tmp/updates:/tmp/updates :LINGUAS=English :BOOT_IMAGE=vmlinuz :LC_COLLATE=C :PWD=/ :MALLOC_PERTURB_=MALLOC_PERTURB_=164 :MALLOC_CHECK_=2
Created attachment 564822 [details] File: anaconda-tb-xJvPop
You can try adding the following to your boot command line: http://dlehman.fedorapeople.org/updates/updates-796013.0.img It should address the immediate issue, but that doesn't mean that you'll be able to use that btrfs filesystem.
David, Can you fill me in on what you mean by" adding the following to your boot command line"? I am not clear on how that works. Also, what is the issue here? The error is pretty non-specific. Thanks, -Erinn
(In reply to comment #3) > David, > Can you fill me in on what you mean by" adding the following to your boot > command line"? I am not clear on how that works. Oh, I see I left out an important piece. I should have said to add the following to the boot/installer command line: updates=http://dlehman.fedorapeople.org/updates/updates-796013.0.img If you're still confused, take a look at this: http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/ch-Boot-x86.html#s2-x86-starting-bootopts and perhaps this: http://fedoraproject.org/wiki/Anaconda/Updates > > Also, what is the issue here? The error is pretty non-specific. Interactive editing of and device containing a btrfs filesystem is currently broken. What will probably happen for F17 is you will be limited to automatic partitioning and kickstart for configuring btrfs filesystems. Of course, this will include preventing errors like the one in this bug report.
The main problem for the moment for btrfs is bug 796511: the btrfs utility is not in the installer's runtime environment, which makes it hard to do much with btrfs volumes. Once that and this bug are fixed, you will still be unable to edit/use your preexisting btrfs volumes, but you will be able to use kickstart to do anything you might want to do with btrfs, including automatic partitioning (autopart --type=btrfs).
Hmmm, ok thanks for the explanation and links to more information. This will make testing harder, but I guess a wipe and re-creation of the partitions sans btrfs is in my future. Thanks again for the info.
Just a note that: http://dlehman.fedorapeople.org/updates/updates-796511.0.img Supposedly contains both this fix and follow on btr problems.
anaconda-17.12-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.12-1.fc17
Package anaconda-17.12-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.12-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-3157/anaconda-17.12-1.fc17 then log in and leave karma (feedback).
Don't know why this never got closed out by the Bodhi bot, but it should have done. btrfs generally works decently in F18 and F19, for the record.