Red Hat Bugzilla – Bug 450169
gfs_controld should read plocks from either dlm or lock_dlm
Last modified: 2009-04-16 19:03:21 EDT
Description of problem:
For bug 450138, the kernel plock code was moved from gfs2 into the dlm.
gfs_controld needs to be adapted to this change, and read plocks from
either lock_dlm (kernels before 5.3), or dlm (kernels 5.3 and later).
The misc device gfs_controld reads/writes has previously been called
"lock_dlm_plock", but the patch for bug 450138 changes the name of
the device to "dlm_plock". gfs_controld looks for "dlm_plock", and
if it's not found, looks for "lock_dlm_plock". If "lock_dlm_plock"
is found, it knows that the filesystem/lockspace id in the plock
structures needs to be translated. Otherwise, the operation of
plocks remains the same.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
I'm waiting to push this change to the RHEL5 branch until the patch
for bug 450138 has been included in the RHEL5 kernel. That patch
includes a new kernel header, dlm_plock.h, that is required for
building the modified gfs_controld.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
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 therefore 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.