Bug 601079
| Summary: | Boot fails with LVM logging to file and / not on LV | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | lvm2 | Assignee: | Milan Broz <mbroz> |
| Status: | CLOSED ERRATA | QA Contact: | Corey Marthaler <cmarthal> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5 | CC: | agk, coughlan, dejohnso, dkovalsk, dmair, dwysocha, fnadge, heinzm, jbrassow, jkortus, joe.thornber, jturner, mbroz, pkeloth, pm-eus, prockai, pvrabec, tao |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.56-8.el5_5.5 | Doc Type: | Bug Fix |
| Doc Text: |
The lvm command used to fail when the log file specified in lvm.conf was not available. This problem is now resolved and the commands simply log the error and continue as if there was no log file specified at all
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-07-08 07:16:20 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: | 592967 | ||
| Bug Blocks: | 556823 | ||
|
Description
RHEL Program Management
2010-06-07 07:52:45 UTC
Fixed in lvm2-2.02.56-8.el5_5.5. *** Bug 603088 has been marked as a duplicate of this bug. *** Wait a second ... the customer is using the lvm that you state fixes this issue.
Since lvm2-2.02.56-8.el5, LVM commands do not accept a non-writable log file [ lvm.conf : log { file = "/var/log/lvm2.log" } ]
Any command will refuse to process.
Unfortunately, the result is that LVM will fail VG activation during boot as root is still read-only during activation.
The boot process works fine if the file = "/var/log/lvm2.log" is commented out.
NOTE: I have reproduced this issue on RHEL6.
Debbie
Apologize.. did not notice the _5.5 at the end of the package name.. lvm2-2.02.56-8.el5_5.5 Still question though.. has this been fixed in RHEL6 or does a new BZ need to be opened since I duplicated the issue there? Thanks, Debbie (In reply to comment #12) > Still question though.. has this been fixed in RHEL6 or does a new BZ need to > be opened since I duplicated the issue there? For RHEL6 - probably not yet fixed in current build, but there will be another build including all these upstream patches. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0510.html Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The lvm command used to fail when the log file specified in lvm.conf was not available. This problem is now resolved and the commands simply log the error and continue as if there was no log file specified at all |