Description of problem: Starting with a disk having the default storage configuration, if the root logical volume is removed and then added, the space allocated for it is zero bytes. This occurs when the capacity is left blank in the add new mount point dialog. When an explicit capacity is entered, including 0, the space allocated is as expected (see below). The GUI offers no help whatsoever as to what a blank capacity means, but in the past, a blank capacity has meant "use all available space". Version-Release number of selected component (if applicable): anaconda-18.36-1.fc18 How reproducible: Always. Steps to Reproduce: Create a 12 GB empty disk image: $ qemu-img create f18-test-2.img 12G Start the Live CD: $ qemu-kvm -m 2048 -hda f18-test-2.img -cdrom ~/xfr/fedora/F18/F18-Beta/Final/Fedora-18-Beta-x86_64-Live-Desktop.iso -usb -vga qxl -boot menu=on -usbdevice mouse Update anaconda and start the installer. Complete an install with the default storage configuration. Restart the installer. Proceed to Manual Partitioning. Click "+" to expand list for Fedora Linux ... Click Root to select. Click "-" to remove. Click Delete It (do not check "Delete all ..."). Click "+" to add new mount point: Mount Point: "/" Capacity: [leave blank] Click Add mount point. Click "+" to expand New ... Installation. Root has size 969.23 kB. Click Apply Changes. Root has size 0 B. Actual results: Zero bytes allocated for Root logical volume. Expected results: Maximum available space is allocated for Root logical volume. Additional info: If a moderate, non-zero capacity, such as 3000, is entered, that much space is allocated for Root. If 12000 is entered for the capacity, 7.75 GB is allocated for Root. If a zero capacity is entered, 1 MB is allocated for Root.
"... the space allocated for it is zero bytes." I meant to say "... the space allocated for it _may be_ zero bytes."
Created attachment 659034 [details] anaconda-tb-all.log Log file captured after clicking Apply Changes: # pkill -USR2 -o anaconda
Here's the key: 16:06:48,167 DEBUG anaconda: requested size = 0 B ; available space = 969.23 kB 16:06:48,228 ERR anaconda: newDevice failed: not enough free space on disks I wonder if _free_space does not reflect the space made available by deleting / the first time. Well, something for tomorrow.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.