Bug 467899
Summary: | Anaconda enforces archaic LVM1 extent limit on LVM2 logical volumes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Snook <csnook> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | atodorov, ddumas, notting, syeghiay |
Target Milestone: | rc | ||
Target Release: | 6.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | anaconda-12.38.5-1.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-02 18:48:17 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: | |||
Bug Depends On: | |||
Bug Blocks: | 472555 |
Description
Chris Snook
2008-10-21 16:13:54 UTC
This should be fixed up in F11, which means it'll get pulled in for RHEL6. I doubt we'll ever be able to isolate the set of commits that fix just this issue for backporting, since fixing this was part of a major storage rewrite we've been dealing with for a while now. If you can, please test F11 out so we can make sure there's no outstanding problem for RHEL6. Thanks. Tested with anaconda-13.21.45-1.el6 in Xen domU. My setup is this: - The domU backing store is a 100G file on the host - In Anaconda UI I've created /boot (200MB) and a PV using all remaining space - Created a VG with PE size 1MB and a LV for / with size 99850 MB. The rest is swap Anaconda didn't issue any warnings or errors and happily proceeded with the install. The system was able to boot after install. Moving to VERIFIED. Red Hat Enterprise Linux Beta 2 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |