Bug 36837
Summary: | Kickstart: too little free space in partitioning causes big mess | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Pekka Savola <pekkas> |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-05-02 05:05:56 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: |
Description
Pekka Savola
2001-04-20 14:22:20 UTC
http://www.redhat.com/support/manuals/RHL-7-Manual/ref-guide/s1-kickstart2-commands.html Take a look at the above URL for kickstart documentation. You can make kickstart do what you want it to by passing in various options. If you want / to be created first, you can use the --onprimary <N> flag. Does this fix your problem? That does not work properly. If you define: part / --size 1024 --onprimary 1 part swap --size 512 [and so on] The auto-partitioning will fail if the partitions exists even though there is 'clearpart --all' with: Failed to allocate '/': No free primary Can you attach your complete kickstart file? Created attachment 16005 [details]
%packges and %post have been snipped as they're of no consequence here
Created attachment 16006 [details]
%packges and %post have been snipped as they're of no consequence here
Created attachment 16007 [details]
packages and post have been snipped as they're of no consequence here
Whoops. Attaching seemed to freeze but apparently it works. I just did a minimal kickstart install with your kickstart file with no problems. Here's what df says on that system: /dev/hda1 1035660 157916 825136 17% / /dev/hda6 1035660 20 983032 1% /config /dev/hda9 3621020 20 3437060 1% /opt /dev/hda8 521748 24 495220 1% /tmp /dev/hda5 3099260 4172 2937656 1% /var Yeah, that works. Try to install on a smaller HDD, like 6.4 GB, and there _should_ be problems. Other way to incite get on the one you currently are using might be to make bigger partitions. I'm guessing: part / --size 2048 part swap --size 512 part /tmp --size 512 part /config --size 2048 part /var --size 4096 part /opt --size 1 --grow would be enough (/opt would be like 600 megs) Reopening just in case. Yes, I see what you mean. A complete rework of the partitioning subsystem is on the drawing board, so I expect this problem to be fixed by that. As such, there's not much use in patching the existing code. Thanks for your report. |