Bug 446260 - HA-LVM: Will not start on ia64, looking for initrd in wrong directory.
Summary: HA-LVM: Will not start on ia64, looking for initrd in wrong directory.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: rgmanager
Version: 5.2
Hardware: ia64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jonathan Earl Brassow
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 446744 455919
TreeView+ depends on / blocked
 
Reported: 2008-05-13 19:44 UTC by Dean Jansa
Modified: 2009-04-16 22:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-20 20:56:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0101 0 normal SHIPPED_LIVE rgmanager bug-fix and enhancements update 2009-01-20 16:04:34 UTC

Description Dean Jansa 2008-05-13 19:44:32 UTC
Description of problem:

HA-LVM will not run on ia64 due to the lvm.sh script looking for initrd in /boot
rather than /boot/efi/efi/redhat.   The resulting error in /var/log/messages is:
 May 13 14:26:42 link-14 clurgmgrd: [5556]: <err> HA LVM requires the initrd
image to be newer than lvm.conf


From lvm.sh:

 # Fixme: we might be able to perform a better check...
        if [ "$(find /boot/*.img -newer /etc/lvm/lvm.conf)" == "" ]; then
                ocf_log err "HA LVM requires the initrd image to be newer than
lvm.conf"
                return $OCF_ERR_GENERIC
        fi


The path in the find needs to be changed for ia64 or something along the lines of:

find /boot -name *.img -newer /etc/lvm/lvm.conf

which should work on all archs.

That find seems a bit suspect as well, as it finds any initrd which is newer
than lvm.conf.  Shouldn't it check the one you booted with is newer?

Comment 1 Jonathan Earl Brassow 2008-05-14 18:08:56 UTC
"That find seems a bit suspect as well, as it finds any initrd which is newer
than lvm.conf.  Shouldn't it check the one you booted with is newer?"

Yes, it should; but how do you find out which initrd was used?  I suppose you
could look in grub... gets a bit crazy.  Perhaps we can start with your suggestion.



Comment 4 errata-xmlrpc 2009-01-20 20:56:07 UTC
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-2009-0101.html


Note You need to log in before you can comment on or make changes to this bug.