linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: error creating snapshots
Date: Tue, 03 Nov 2009 17:17:52 +0000	[thread overview]
Message-ID: <1257268672.6488.145.camel@breeves.fab.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0911031147050.30149@bmsred.bmsi.com>

On Tue, 2009-11-03 at 11:48 -0500, Stuart D. Gathman wrote:
> On Tue, 3 Nov 2009, Mike Snitzer wrote:
> 
> > > # lvcreate -s -L20G -n dmm_snap bms_data/dmm
> > >   bms_data-dmm_snap: event registration failed: 10071:3 
> > > libdevmapper-event-lvm2snapshot.so dlopen failed: 
> > > /usr/lib64/liblvm2cmd.so.2.02: undefined symbol: dm_list_empty
> > >   bms_data/snapshot0: snapshot segment monitoring function failed.
> > >   Logical volume "dmm_snap" created
> > 
> > This is harmless but it does mean that dmeventd-based snapshot
> > usage monitoring is not currently enabled for this snapshot.
> > 
> > But if you restart dmeventd (kill the process and it'll restart next
> > time you activate the snapshot) it should work.
> 
> How can restarting a daemon make a library symbol suddenly become defined?
> Isn't this a library issue?
> 

If the daemon has been running since before the package update it will
still use the old binary/library images. Killing and re-starting it will
force it to use the newly updated versions.

Regards,
Bryn.

  reply	other threads:[~2009-11-03 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  3:35 [linux-lvm] error creating snapshots Stuart D. Gathman
2009-11-03 14:16 ` [linux-lvm] " Mike Snitzer
2009-11-03 14:50   ` Stuart D. Gathman
2009-11-03 14:54     ` Stuart D. Gathman
2009-11-03 16:48   ` Stuart D. Gathman
2009-11-03 17:17     ` Bryn M. Reeves [this message]
2009-11-03 17:17       ` Stuart D. Gathman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1257268672.6488.145.camel@breeves.fab.redhat.com \
    --to=bmr@redhat.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).