|Summary:||[RFE] Improve robustness of storage allocation|
|Product:||[Fedora] Fedora||Reporter:||Marian Csontos <mcsontos>|
|Component:||python-blivet||Assignee:||David Lehman <dlehman>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||agk, amulhern, anaconda-maint-list, bcl, dlehman, g.kaviyarasu, jonathan, vanmeeuwen+fedora|
|Fixed In Version:||python-blivet-0.44-1||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2014-03-31 21:25:50 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Marian Csontos 2014-02-13 11:05:24 UTC
Anaconda tries to create whole storage layout and then commit it in one transaction. This is not an easy problem and sometimes goes wrong because the free space is short of just a few megabytes. As discussed in Brno the LVM team is trying to make some changes to address the issue but there will be still cases (e.g. mdraid and crypt-setup devices) which won't be handled. Recalculating volume sizes according to remaining free space after every step would fix these failures and make anaconda more robust. There are further constraints which anaconda is aware of and is the one who should ensure they are met: 1. system disk MUST be able to hold installed packages 2. smaller volumes SHOULD be allocated first as being few 100 megabytes short on large volumes is less an issue than on very small partitions like /boot
Comment 1 Brian Lane 2014-02-14 16:29:16 UTC
Note that is would be *very* useful if the storage systems like lvm and mdadm were able to accurately report what they are going to use instead of us having to guess and fudge.
Comment 2 David Lehman 2014-03-31 21:25:50 UTC
Blivet should now correct LV sizes as needed before creating them based on VG free space.