Bug 585364
Summary: | Use of --grow in kickstart partitioning results in / on second disk | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> | ||||
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: | 13 | CC: | anaconda-maint-list, jonathan, vanmeeuwen+fedora | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-04-23 19:57:18 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: | |||||||
Attachments: |
|
--grow without a maxSize tells kickstart to grow it as large as possible. Since there's more space on your second disk (what with /boot and swap being on the first), it prefers to move the / partition over to that disk. |
Created attachment 408712 [details] storage.log Description of problem: This is surprising to me, although perhaps it is intended behavior. The following kickstart partitioning: clearpart --linux part /boot --size=200 part / --size=12000 --grow part swap --recommended on a system with more than one disk results in / being on different disk. Also present in RHEL 6 beta.