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 451816 - CMAN init script must not try to load lock_dlm
Summary: CMAN init script must not try to load lock_dlm
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman
Version: 5.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Robert Peterson
QA Contact: Cluster QE
Depends On: 447748
TreeView+ depends on / blocked
Reported: 2008-06-17 16:24 UTC by Robert Peterson
Modified: 2009-04-16 23:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-06-26 15:19:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Robert Peterson 2008-06-17 16:24:46 UTC
Description of problem:
We're splitting out the locking protocols between gfs and gfs2.
Even though it's in the gfs2 kernel source tree, lock_dlm module will
now only look for gfs 1's gfs-kernel "gfs_register_lockproto".
Therefore, the cman init script cannot automatically load it as before.

The loading of lock_dlm either needs to be done from the gfs init
script or not at all (and let the module dependencies take care of it).

Version-Release number of selected component (if applicable):
RHEL5.3 plus the fix for bug #447748 

How reproducible:

Steps to Reproduce:
1. service cman start

Actual results:
[root@exxon-01 ../fs/gfs2]# service cman start
Starting cluster: 
   Loading modules... failed
FATAL: Error inserting lock_dlm
(/lib/modules/2.6.18-prep/extra/locking/dlm/lock_dlm.ko): Unknown symbol in
module, or unknown parameter (see dmesg)
On the console or in dmesg:
lock_dlm: Unknown symbol gfs_register_lockproto
lock_dlm: Unknown symbol gfs_unregister_lockproto

Expected results:
[root@exxon-01 ../fs/gfs2]# service cman start
Starting cluster: 
   Loading modules... done
   Mounting configfs... done
   Starting ccsd... done
   Starting cman... done
   Starting daemons... done
   Starting fencing... done
                                                           [  OK  ]

Additional info:

Comment 1 David Teigland 2008-06-24 17:13:33 UTC
How about the cman init script modprobe's gfs, then modprobe's lock_dlm,
and ignores any failures?

Comment 2 Robert Peterson 2008-06-26 15:19:01 UTC
The decision was made to keep the lock_dlm in place for GFS2 and split
it off by cloning it for the GFS1 package.  Therefore, lock_dlm will
still be in place, at least for 5.3.  Therefore, we don't need to change
the init script.  Closing as NOTABUG.

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