---Problem Description--- While installing 'manual partitioning + LVM' on implicit partition devices the free space shown is not matching the expectations ---uname output--- 3.3.0-0.20.el7 Machine Type = 2817 ---Steps to Reproduce--- 1. To support installation on 'implicit partition devices like FBA, EDEV etc.,' have to install the patches from bugzilla "Bug 84317 - RH707027 - RFE: Installation on Z/VM EDEV failed during format" * what I mean for 'implicit partition' is the whole disk will be of one partition (at maximum). 2. Try installation using 'LVM' and 'Manual partition'. 3. If the whole disk is of '200GB' and 1GB is assigned to '/boot' the free space is shown as '0B'. But the expected value is '199GB'. 4. Reason could be when reading the remaining free space it's not reading from 'volume group' instead reading from disk. Supporting my argument: 4.1 file 'pyanaconda/ui/gui/spokes/storage.py' having function named '_update_summary' which calls the following code for getting the free space. free_space = self.storage.getFreeSpace(disks=self.disks) 4.2 definition of the above function is in file 'pyanaconda/storage/__init__.py' which calls disk_free = disk.format.free 4.3 definition of the 'free' is in file 'pyanaconda/storage/formats/disklabel.py' In this function the free space is calculated by getting the information from disk. 5. For 'implicit partition' kind of disks read the free space from 'volume group' for correctness.
Created attachment 671402 [details] EDEV manual parition + LVM
------- Comment From vaish123.com 2013-01-02 12:01 EDT------- FYI, The link http://fedoraproject.org/wiki/Common_F18_bugs#Installer_crashes_with_degraded.2Fincomplete_RAID.2C_LVM_or_btrfs_devices_present on Common F18 bugs mentions about installer issues with LVM devices present.
Can you please test this again with F19 alpha and if it is still broken, attach a picture of what you are seeing and the new /tmp/storage.log? Thanks.
------- Comment From nasastry.com 2013-06-04 05:52 EDT------- (In reply to comment #10) > Can you please test this again with F19 alpha and if it is still broken, > attach a picture of what you are seeing and the new /tmp/storage.log? > Thanks. Tested with Fedora 19 - 20130528, it is still broken. And going to attach the required screen shot + storage logs. Thanks!!
Created attachment 756622 [details] screen shot ------- Comment (attachment only) From nasastry.com 2013-06-04 05:54 EDT-------
Created attachment 756624 [details] F19 storage log ------- Comment (attachment only) From nasastry.com 2013-06-04 05:57 EDT-------
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days