Bug 182667 - Suppress error message in rc.sysinit for failing to load external locking library
Suppress error message in rc.sysinit for failing to load external locking lib...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2 (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Alasdair Kergon
Cluster QE
: 182668 182669 (view as bug list)
Depends On:
Blocks: 181409
  Show dependency treegraph
Reported: 2006-02-23 17:10 EST by Travis Tiedemann
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2006-0504
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-10 17:45:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Travis Tiedemann 2006-02-23 17:10:32 EST
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):

How reproducible:

Steps to Reproduce:
1. install gfs
2. boot system

Actual Results:  the abovementioned error, but everything mounts fine.

Expected Results:  no error

Additional info:
Comment 1 Christine Caulfield 2006-02-27 10:29:47 EST
*** Bug 182668 has been marked as a duplicate of this bug. ***
Comment 2 Christine Caulfield 2006-02-27 10:29:59 EST
*** Bug 182669 has been marked as a duplicate of this bug. ***
Comment 3 Alasdair Kergon 2006-03-08 13:28:04 EST
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.
Comment 4 Alasdair Kergon 2006-04-03 14:38:07 EDT
Changed upstream.
Comment 10 Red Hat Bugzilla 2006-08-10 17:46:04 EDT
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.


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