Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163857 - Using generates broken initrd images (kernel panic)
Summary: Using generates broken initrd images (kernel panic)
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: lvm2-cluster
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
Depends On:
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:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-07-22 13:18:03 UTC

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/"

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

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.See above
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.