Description of problem: When attempting to install F18 from the live media, I am not given an option about how big to actually make the LV that is being created for my various mount points. Version-Release number of selected component (if applicable): F18 How reproducible: 100% Steps to Reproduce: 1. Choose a custom partition scheme on installation 2. Create a "new" volume group Actual results: No choice is given as to the size of the partition on disk to contain this volume group. Expected results: Some type of interactive LVM dialogue. Additional info: This is an extremely huge feature regression from prior Anaconda versions.
You most certainly can set the size of a logical volume (LV). That's the size you punch in when you create a new mountpoint. Are you saying you cannot choose the size of the entire volume group (VG)?
Sorry, was out of the country. You can specify the sizes for individual mount points, which effectively sets the size of that LV: [root@t510dora ~]# lvdisplay --- Logical volume --- LV Path /dev/130304_f18/swap LV Name swap VG Name 130304_f18 LV UUID 1Qu8dD-d10i-kDTi-0YFS-FcH2-svZV-SMAHfi LV Write Access read/write LV Creation host, time localhost, 2013-03-04 21:27:21 -0500 LV Status available # open 2 LV Size 3.67 GiB Current LE 940 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Path /dev/130304_f18/home LV Name home VG Name 130304_f18 LV UUID 47A5Uv-bHRw-5qoj-xkVk-oImS-YT3E-vnpJmQ LV Write Access read/write LV Creation host, time localhost, 2013-03-04 21:27:21 -0500 LV Status available # open 1 LV Size 97.65 GiB Current LE 24999 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 --- Logical volume --- LV Path /dev/130304_f18/root LV Name root VG Name 130304_f18 LV UUID wKbK4e-5T17-xD5b-yulD-MS0f-Jhye-YbWKff LV Write Access read/write LV Creation host, time localhost, 2013-03-04 21:27:24 -0500 LV Status available # open 1 LV Size 50.00 GiB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 But you don't get to specify the size of the VG, as you stated: [root@t510dora ~]# vgdisplay --- Volume group --- VG Name 130304_f18 System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 151.32 GiB PE Size 4.00 MiB Total PE 38739 Alloc PE / Size 38739 / 151.32 GiB Free PE / Size 0 / 0 VG UUID BjcA9j-tOjQ-TlWf-EZtB-eucR-aEXe-ipkXl2 This is basically the sum of the LVs. The resultant single PV/partition is also the same: [root@t510dora ~]# pvdisplay --- Physical volume --- PV Name /dev/mapper/luks-1952b138-c5d1-4735-a793-aa911742b272 VG Name 130304_f18 PV Size 151.33 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 38739 Free PE 0 Allocated PE 38739 PV UUID xV8AL5-r4fb-gaXH-hS8d-7Vlb-9jxn-jYz5dd So I guess my description is off. You can't specify the PV or VG sizes during installation. I will update that now.
*** Bug 928747 has been marked as a duplicate of this bug. ***
As of anaconda-19.24-1 it is possible to choose one of three sizing policies for lvm volume groups and btrfs volumes: 1. automatic: the f18 behavior 2. as large as possible: grow the vg as large as possible, regardless of the lv sizes 3. fixed: specify a fixed size for the vg This new functionality will be in the F19 Beta, so please give it a try when the beta is released. If you encounter bugs in the functionality, please open bug reports for them instead of commenting in this bug. Thanks.