Red Hat Bugzilla – Bug 454349
appears that dmevent needs to be restarted
Last modified: 2010-01-11 22:54:16 EST
Description of problem:
Otherwise you'll end up with the following messages over and over while doing
event registration failed: 30718:9 libdevmapper-event-lvm2mirror.so dlopen
failed: /lib64/libdevmapper-event-lvm2mirror.so: undefined symbol: lvm2_run
Version-Release number of selected component (if applicable):
lvm2-2.02.39-1.el5 BUILT: Thu Jul 3 08:41:39 CDT 2008
lvm2-cluster-2.02.39-1.el5 BUILT: Thu Jul 3 09:31:57 CDT 2008
device-mapper-1.02.27-1.el5 BUILT: Thu Jul 3 03:22:29 CDT 2008
There is a slight problem with dmeventd restart, since we have to re-register
all the monitored volumes and I don't think there currently is a way to do so
reliably. But we likely want to fix that for 5.3.
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
Even if there is only warning about need of re-activate volumes to start
monitoring for them is better than dmeventd in non-functional state because of
Current proposed fix (it is a little ugly, beut should work):
1) Make the "to be monitored" a persistent logical volume property.
2) This can be non-intrusively (in a backward-compatible manner) done by adding
an inverted flag to metadata (say NOMONITORING): if the flag is cleared, it
means that the device will be (if possible) monitored (which is the default)
and when it is set, the device is excluded from monitoring.
3) Add a vgchange (sub-)command to register all applicable LVs for
monitoring -- this can then be used for starting dmeventd after upgrades.
We do 2) to avoid having to flag existing devices upon upgrade, as Milan
pointed out, a possibly dangerous operation.
I restarted dmeventd and still ended up seeing these errors, could this be a
ok, that issue was caused by broken build, it is fixed in lvm2-2.02.39-2.el5
I'll clone separate bug for dmeventd restart, just to not forget ideas :)
Fix verified in lvm2-2.02.39-2.el5.
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.