Bug 191879
Summary: | Boot fails if any logical volume is exported | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Bob Gautier <bob.gautier> | ||||
Component: | initscripts | Assignee: | Miloslav Trmač <mitr> | ||||
Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | CC: | agk, dwysocha, formisc, mbroz, notting, pjones | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHBA-2007-0303 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-05-01 17:29:05 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
Bob Gautier
2006-05-16 09:56:12 UTC
Are there other cases it would return non-zero when it actually did not fail? lvm2 reports the most severe error it found for anything it was asked to do. For vgscan during startup, it's probably best to ignore errors and proceed to the vgchange regardless: A failure in vgscan does not necessarily mean that vgchange won't succeed. I suppose the reason that's there is that if you don't catch any errors, you get a nice: 'Setting up logical volume management: No volume groups found' message on every boot. Is anything going to happen with this? This problem prevents systems booting, and as you point out, removing the error test would still produce a useful message at boot-time if something was really wrong. No, what I'm saying is that you remove the test, you get an error/warning message on every boot when it *is* working fine, which isn't really what you want. When I boot with a patched rc.sysinit (which I'll attach), I get exactly what I expect: Setting up logical volume management: Ok I think I'd only get the message 'No volume groups found' if I actually had no volume groups, or if they were all exported. Created attachment 134447 [details]
Patched rc.sysinit that avoids vgscan
This is simply the stock rc.sysinit with references to vgscan removed.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Added in CVS, will be in 7.93.26.EL-1 or later. The patch leaves an ugly FAILED in the boot output: Setting up Logical Volume Management: Volume group "vg2" is exported 1 logical volume(s) in volume group "vg1" now active [FAILED] Still, this is probably better than ignoring real LVM setup failures when no VGs are exported. The exit code of vgchange is undocumented, so initscripts can't distinguish between an exported volume and other errors. 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 the 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-2007-0303.html I seemed to have a similar issue during the _installation_ of version 6. i have a system with a few VG (LVM2). to preserve the content of one of the VG i followed the LVM FAQ (http://tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html): 1. umount ; 2. vgchange -ay 3. vgexport 4. updated /etc/fstab to comment out the VG. Affter reboot the VG reports to be in non-active status and FS is not mounted. after i start the network install and it comes to checking the available drives, anakonda throws an exception - "can't activate exported VG". And the installer terminates. I understand that i can physically unplug the drives, but that's not a good enough solution. Please advise. Andrew |