Hide Forgot
== Comment: #0 - Khushboo Srivastava <khusriva.com> - 2013-11-07 07:31:30 == -----------------Description-----------------:- On selecting the multiple disk for installation it is giving space mismatch the available space is more than the total space. If you delete the existing partition manually you can see the good amount of available space but on clicking on automatic partition it is giving automatic partitioning error because of no space --------------How reproducible--------------: It is reproducible often. ---------Version-Release number of selected component like OS, packages etc (if applicable)----------: [root@miz10 ~]# uname -a Linux miz10.austin.ibm.com 3.11.5-302.fc20.ppc64 #1 SMP Wed Oct 16 15:10:40 MST 2013 ppc64 ppc64 ppc64 GNU/Linux [root@miz10 ~]# the link is :- http://ppc.koji.fedoraproject.org/stage/f20-20131021-Beta-TC5.1/Fedora/ppc64/iso/Fedora-20-ppc64-DVD.iso -------------Steps to Reproduce------------------: 1) Boot from virtual DVD of Fedora20 ppc64 2) Proceed for VNC installation 3) Reclaim space if any 4) select two disks for installation 5) Make sure partition scheme LVM must be selected and "I want to review or modify disk partitions before continuing" must be enabled . 6) click on continue 7) On Manual Partition Scheme page, notice the available size and total size. 8) Manually delete all the existing partition. 9) now try to click for automatic create partition 10) it will automatically create the unknown partition which we deleted manually and it will through an error for automatic partitioning failed due to no available space. ---------------Actual results-------------------------- Giving Automatic partitioning failed error with space mismatch --------------------Expected Results------------------ It should create the automatic partition without any error ---------------------Additional info----------------------------- Please find the attachment for the screen shots and related logs
Created attachment 821768 [details] screenshot1
Created attachment 821769 [details] screenshot2
Created attachment 821770 [details] screenshot3
Created attachment 821771 [details] screenshot4
Created attachment 821772 [details] screenshot5
Created attachment 821773 [details] screenshot6
Created attachment 821774 [details] screenshot7
Created attachment 821775 [details] screenshot8
Created attachment 821776 [details] screenshot9
Created attachment 821777 [details] screenshot10
Created attachment 821778 [details] screenshot11
Created attachment 821779 [details] screenshot12
Created attachment 821780 [details] screenshot13
Created attachment 821782 [details] screenshot14
Created attachment 821783 [details] screenshot15
Created attachment 821784 [details] screenshot16
Created attachment 821785 [details] screenshot17
Created attachment 821786 [details] anaconda logs
Created attachment 821787 [details] anaconda-yum.conf
Created attachment 821788 [details] ifcfg.log
Created attachment 821789 [details] program.log
Created attachment 821790 [details] syslog
Created attachment 821791 [details] storage.log
------- Comment From gusld.com 2013-11-13 16:58 EDT------- I could not reproduce this issue using Fedora 20 Beta. Could you please try that and let us know if this issue is fixed there?
------- Comment From khusriva.com 2013-11-14 08:43 EDT------- The issue is resolved in Fedora20-Beta.
Closing per comment 25