Bug 163857 - Using liblvm2clusterlock.so generates broken initrd images (kernel panic)
Summary: Using liblvm2clusterlock.so generates broken initrd images (kernel panic)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: lvm2-cluster
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-21 16:44 UTC by Axel Thimm
Modified: 2010-01-12 04:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-07-22 13:18:03 UTC
Embargoed:


Attachments (Terms of Use)

Description Axel Thimm 2005-07-21 16:44:35 UTC
Description of problem:
or making use of clvmd one needs to change lvm.conf to include

    locking_type = 2
    locking_library = "/usr/lib64/liblvm2clusterlock.so"

kernels installed later will mkinitrd with this config file which will make the
kernel panic.

Version-Release number of selected component (if applicable):
2.01.09-5.0.RHEL4

How reproducible:
always

Steps to Reproduce:
1.See above
2.
3.
  
Actual results:
kernel panic on reboot

Expected results:


Additional info:
lvm in initrd is statically linked but the cluster locking mechanisms are
dynamically loaded even so. The initrd should contain a different version of
lvm.conf than the filesystem.

Comment 1 Axel Thimm 2005-07-22 13:18:03 UTC
The initrd was broken due to bad udev/qla2300 interaction, sorry for the noise ... 


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