From: Mike Snitzer <snitzer@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Re: error creating snapshots
Date: Tue, 3 Nov 2009 09:16:26 -0500 [thread overview]
Message-ID: <20091103141626.GA15344@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0911022226110.26129@bmsred.bmsi.com>
On Mon, Nov 02 2009 at 10:35pm -0500,
Stuart D. Gathman <stuart@bmsi.com> wrote:
> Is this a harmless error having to do with some misreported option to notify a
> user process when the snapshot is almost full? Or should I switch backups over
> to network based because this means LVM might corrupt data?
>
> CentOS-5.4
>
> # uname -a
> Linux xerces.jsconnor.com 2.6.18-164.el5xen #1 SMP Thu Sep 3 04:03:03 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
> # 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.
I'll have a look at how best to cope with this within lvm2 (either
rpm upgrade triggers or...). But out of curiosity: had you upgraded
lvm2 (lvm2-libs et al) prior to creating the snapshot and dmeventd was
running prior to the upgrade?
Mike
next prev parent reply other threads:[~2009-11-03 14:16 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 ` Mike Snitzer [this message]
2009-11-03 14:50 ` [linux-lvm] " 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
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=20091103141626.GA15344@redhat.com \
--to=snitzer@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).