Description of problem: When click back and forth between two mount points, the size of one of the mount points changes to to a different value with each click. Erratic behavior. Version-Release number of selected component (if applicable): anaconda 19.24-1 How reproducible: Intermittant Steps to Reproduce: 1. Choose four disks as targets for installation. 2. Installation options, choose partition scheme BTRFS 3. Manual partitioning, create two mount points each with their own BTRFS volume, one raid0, one raid1. 4. Click back and forth between the two mount points. Actual results: /home mount point size changes with each back and forth click. Expected results: I expect the size to remain stable until the user makes a change. Additional info:
Created attachment 743668 [details] anaconda.log
Created attachment 743669 [details] program.log
Created attachment 743670 [details] storage.log
Created attachment 743671 [details] storage.state
The mount point whose size changes with each click, is in a volume configured with a Size Policy of "as large as possible". So in addition to size being erratic, it's also incorrect as there's still ~1.62 TB of available space.
Bug 959725 filed for the 2nd line of comment 5.
Now that you can directly control the size of the volume we shouldn't be allowing changes to the size entry for subvols. There are a few changes that go along with that, though, which will take some time to sort out. I suppose I could fix the immediate bug here in the meantime.
anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19
Package anaconda-19.27-1.fc19, pykickstart-1.99.31-1.fc19, python-blivet-0.14-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.27-1.fc19 pykickstart-1.99.31-1.fc19 python-blivet-0.14-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.27-1.fc19 then log in and leave karma (feedback).
Package pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing pykickstart-1.99.31-1.fc19 anaconda-19.28-1.fc19 python-blivet-0.14-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8322/python-blivet-0.14-1.fc19,pykickstart-1.99.31-1.fc19,anaconda-19.28-1.fc19 then log in and leave karma (feedback).
pykickstart-1.99.31-1.fc19, anaconda-19.28-1.fc19, python-blivet-0.14-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.