From: Zdenek Kabelac <zkabelac@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Error message:lib64/libdevmapper-event-lvm2snapshot.so.2.02: undefined symbol: lvm2_run
Date: Fri, 09 Apr 2010 21:55:38 +0200 [thread overview]
Message-ID: <4BBF863A.8030508@redhat.com> (raw)
In-Reply-To: <20100407052739.GA16693@maude.comedia.it>
On 7.4.2010 07:27, Luca Berra wrote:
> On Tue, Apr 06, 2010 at 03:48:39PM -0700, Linda A. Walsh wrote:
>>
>> I am trying to run a 2.6.33.1 kernel with a Suse11.2 runtime, which
>> I think uses a 2.6.31.12 kernel.
>>
>> Has some user-space library changed that I need to rebuild so I can use
>> the newer kernel, or ---
>> WHAT the heck is going on?! :-)
>>
>> Entire error message (and related messages) from logs:
>>
>> Home-2010.04.05--18.00.01: event registration failed: 22892:9
>> libdevmapper-event-lvm2snapshot.so.2.02 dlopen failed:
>> /lib64/libdevmapper-event-lvm2snapshot.so.2.02: undefined symbol:
>> lvm2_run
>> Home/snapshot0: snapshot segment monitoring function failed.
>>
>> Thanks for any pointers in telling me how to go about fixing this
>> new snafu!
>> Sigh...
>> Suse 11.2 has been such a pain to upgrade to!
> looks like underlinking of libdevmapper-event-lvm2snapshot.so.2.02
> it should be linked to liblvm2cmd.so.2.02
> open a bug report vs your vendor
Yes there are ongoing cleanups of linkage process, to keep the amount
of linked libraries at minimum level.
libdevmapper-event-lvm2.so.2.02 should have dependency on liblvm2cmd.so.2.02.
See WHATS_NEW/2.02.59 for the reason of libdevmapper-event-lvm2.
Zdenek
prev parent reply other threads:[~2010-04-09 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:48 [linux-lvm] Error message:lib64/libdevmapper-event-lvm2snapshot.so.2.02: undefined symbol: lvm2_run Linda A. Walsh
2010-04-07 5:27 ` Luca Berra
2010-04-09 19:55 ` Zdenek Kabelac [this message]
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=4BBF863A.8030508@redhat.com \
--to=zkabelac@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).