Description of problem: When I choose btrfs for a mount point(/ or /home) I received following exception. anaconda 17.5 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 946, in addDevice btrfs_dev = self.storage.devicetree.getChildren(device)[0] File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1096, in populate self.addDevice(device, iter) File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1649, in refresh self.populate() File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1712, in editPartition if self.refresh(justRedraw=not actions): File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1587, in createCB self.editPartition(device, isNew = True) IndexError: list index out of range I made disk image by qemu-img command without "-f" option so that its format should be raw. Version-Release number of selected component (if applicable): Fedora 17 Alpha TC1 x86_64 I downloaded it from here. http://dl.fedoraproject.org/pub/alt/stage/17-Alpha.TC1/Fedora/x86_64/iso/Fedora -17-Alpha-x86_64-DVD.iso How reproducible: always Steps to Reproduce: 1. Select "Create Custom Layout" in 'Disk Partitioning Setup' screen 2. Add a partition and Choose btrfs for '/' then click OK button Actual results: Receive IndexError exception Expected results: Can use btrfs
Created attachment 559397 [details] Anaconda log
this still happens in tc2 x86, and it also happens if the target system already has btrfs partitions on it.
*** Bug 787565 has been marked as a duplicate of this bug. ***
reproduced with F17 Alpha RC2 when create partition with type btrfs
I also could reproduce the bug. RC2 i386 netinstall. Happens when installing inside a VM (F16 host with VirtualBox). Haven't tried a native install.
Proposing as a Final blocker: it's at least that, per criterion "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" . The fact it crashes on systems with existing btrfs partitions is also worrying. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
still present on alpha rc3 netinstall. i tried in virtualbox, too.
*** Bug 795670 has been marked as a duplicate of this bug. ***
*** Bug 796071 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > *** Bug 796071 has been marked as a duplicate of this bug. *** Reproduced with F17 Alpha RC4
reproduced creating simple partition layout--500M swap and 9500M btrfs partition... i686 guest on kvm.
(In reply to comment #11) > reproduced creating simple partition layout--500M swap and 9500M btrfs > partition... i686 guest on kvm. F17-RC4-i686
*** Bug 796665 has been marked as a duplicate of this bug. ***
Once bug 796511 and bug 796013 are resolved, you will still be unable to create btrfs filesystems using the custom partitioning interface in anaconda. You will, however, be able to create btrfs volumes using kickstart: https://fedoraproject.org/wiki/Anaconda/Kickstart#btrfs Also, note the availability of a btrfs automatic partitioning scheme, also available only via kickstart: https://fedoraproject.org/wiki/Anaconda/Kickstart#autopart (autopart --type=btrfs) Meanwhile, I'll be trying to make the custom partitioning side work more smoothly.
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 798750 has been marked as a duplicate of this bug. ***
*** Bug 798780 has been marked as a duplicate of this bug. ***
Couldn't create btrfs volumes with kickstart either.
(In reply to comment #19) > Couldn't create btrfs volumes with kickstart either. You can create btrfs volumes just fine with kickstart -- just not with encrypted member devices.
Created attachment 568205 [details] ks file btrfs does not work with the ks file in attachment
Chris, Brian - I know this bug only *blocks* Final, but it sure would be nice to have it fixed for Beta, if you could manage it... -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #21) > Created attachment 568205 [details] > ks file > > btrfs does not work with the ks file in attachment That's correct, because btrfs is not just a filesystem. For now, you'll have to create a btrfs volume as described here: https://fedoraproject.org/wiki/Anaconda/Kickstart#btrfs
I get this with F17 Beta TC1 x86_64 netinst.iso, anaconda 17.12. With or without LVM. With or without encryption.
*** Bug 803733 has been marked as a duplicate of this bug. ***
anaconda-17.14-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.14-1.fc17
Package anaconda-17.14-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.14-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4546/anaconda-17.14-1.fc17 then log in and leave karma (feedback).
anaconda-17.14-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
how is one supposed to use the updated anaconda if it's not on an install disc/media? if no such media is available, how do you know this is fixed?
(In reply to comment #29) > how is one supposed to use the updated anaconda if it's not on an install > disc/media? if no such media is available, how do you know this is fixed? It will be on install media: F17-Beta. It still may not be "fixed" in the way you hope for. As I stated in comment 14, there will still be no support for creating or editing btrfs filesystems in F17-Beta, except via kickstart.
Thank you for clarifications, David.
17.14 is in Beta RC1. Bodhi automatically closes any bug an update is marked as 'fixing' when that update is pushed stable. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This bug was closed automatically by Bodhi, but we still need to verify it. Changing status to ON_QA.
Confirming that this is 'fixed' in the sense that btrfs isn't on the list of available filesystems in custom partitioning in 17 Beta RC1. We should probably document this in the release notes for 17. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
thank you all very much.
I also tested that upgrading a system which has btrfs already works okay.
Installing with a kickstart file on a multiboot system with different partitions doesn't work if you don't delete all existings partitions. My partitioning schema in ks.cfg. # Disk partitioning information ignoredisk --drives=sda1,sda3,sda4,sda5,sda6,sda7,sda8,sdb1,sdb2,sdb3,sdb5,sdb6 part /boot --fstype ext4 --grow --noformat --onpart=sda2 --size=1 part / --fstype btrfs --grow --maxsize=30000 --ondisk=sda --size=1 Here i have 40GB left at the end of the disk. Installation fails with 'can't create disk'. With a existing unformatet disk: # Disk partitioning information part /boot --fstype ext4 --grow --noformat --onpart=sda2 --size=1 part / --fstype btrfs --grow --ondisk=sda4 --size=1 ends up with 'can't create a filessystem because it's mounted read only'. The only thing what's work with a existing btrfs is # Disk partitioning information part /boot --fstype ext4 --grow --noformat --onpart=sda2 --size=1 part / --fstype btrfs --grow --noformat --ondisk=sda4 --size=1 But after the minimal installation is finished i can't do nothing as root in runlevel 3 because the filesystem is read only mounted. I found a workaround, see http://forums.fedoraforum.org/showthread.php?t=278404 But this isn't a real solution. In my eyes you doesn't fixed the issue really. This is fc17 use blocker for people who havea a sdd disk. Maybe i'm wrong and i have a error in my ks.cfg but i had tried many versions. ks.cfg is appended.
Created attachment 575522 [details] ks.cfg raveit65