From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Union Pacific Corporate Image; SV1; .NET CLR 1.1.4322) Description of problem: We have a three node cluster running RHEL 4 U2 and GFS 6.1. The servers are G4 Proliant DL380s running dual Emulex 9802 HBAs and mpio. They are connecting via McData switches to an older Symmetrix box. When the systems boot, I see the following error: Setting up logical volume management: unable to open external locking library liblvm2clusterlock.so Locking inactive: ignoring clustered volume group vgtest 6 logical volumes in volume group "Volume00" now active This appears to come from the stanza in rc.sysinit which begins: # LVM2 initialization Later on, when the cluster suite/GFS scripts run, the GFS filesystem is mounted just fine. I think this is just a cosmetic/timing issue. Version-Release number of selected component (if applicable): lvm2-cluster-2.01.14-1.0.RHEL4 How reproducible: Always Steps to Reproduce: 1. install gfs 2. boot system Actual Results: the abovementioned error, but everything mounts fine. Expected Results: no error Additional info:
*** Bug 182668 has been marked as a duplicate of this bug. ***
*** Bug 182669 has been marked as a duplicate of this bug. ***
Did you retype that? My version has 'Logical Volume Management' capitalised. I suppose lvm.static (or --ignorelockingfailure) should suppress the 'unable to open' error message.
Changed upstream.
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-2006-0504.html