Bug 485276
Summary: | Kickstart partitioning odity | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | A.J. Werkman <aj.werkman> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | anaconda-maint-list, jgranado |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-03 11:25:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
A.J. Werkman
2009-02-12 18:08:35 UTC
What happens if you specify a minimum size for part pv.7? Or if you tell it what disk to be on? At the moment I can not reproduce because in anaconda 11.5.0.19 that is now in my rawhide tree I get an exception as reported in bug #485565. I will trie later when I receive a newer anaconda in rawhide Chris, Specifying a minimum size know is obligatory (anaconda 11.5.0.59, F11). When I tell pv.7 what disk to be on, it follows my orders, ie. when I use ondisk=sda, then the boot and the pv.7 with root whill be on sda and sdb is left blank. But the point of my bug report is, that when I give no specification on where to put everything, anaconda does not install according to sense. As I said before logic would mean to me, that either anaconda in that case would only use the first disk to install on, or it would use both discs, and use the entire disk space. Altough on second thought I think the second option is not valid. Since I define only one physical volume in my kickstart file and using both disks would mean there have to be two logical volumes. So this leaves only my first option, anaconda should not put pv.7 on the second disc, but use the first disk where it already as placed the boot partition. This however leaves the question if I want fedora to be installed on all diskspace in the system, what exact command could be used in a kickstart file. Starting with the fact, that when creating the kickstart file I do not know the number of discs that will be in every system using that kickstart file. So I do not know how many "part pv" commands I have to enclose. (In reply to comment #3) > Chris, > > Specifying a minimum size know is obligatory (anaconda 11.5.0.59, F11). ... > But the point of my bug report is, that when I give no specification on where > to put everything, anaconda does not install according to sense. "according to sense" here is very Subjective. To me it makes perfect sense to maximize the size of the PV and use the second drive. In this way your installation will have more space. > > As I said before logic would mean to me, that either anaconda in that case ... > This however leaves the question if I want fedora to be installed on all > diskspace in the system, what exact command could be used in a kickstart file. > Starting with the fact, that when creating the kickstart file I do not know the > number of discs that will be in every system using that kickstart file. So I do > not know how many "part pv" commands I have to enclose. I believe you can use autopart. See http://fedoraproject.org/wiki/Anaconda/Kickstart I'm closing this bug because of 2 reasons: 1. There are 2 workarounds: 1. using autopart, and 2. specifying the disk for the PV. 2. The required behavior is a matter of opinion. As I said previously, it is perfectly sensible to maximize partition size. |