From: Falk Hackenberger - MediaTransfer AG Netresearch & Consulting <f.hackenberger@mediatransfer.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm2 with clusterlock problems with snapshot
Date: Mon, 23 Jan 2006 11:48:56 +0100 [thread overview]
Message-ID: <43D4B498.4000306@mediatransfer.com> (raw)
hello,
i plan to setup a fileserver with 2 nodes for ha and 1 san-device for
storege.
Bescause the san-device have noch snapshot option (budget), ihave to
snapshot with lvm2 for backup.
so my testsetup with onde node works fine, exept the snapshot.
if I try to snapshot I get
root@kain ~]# lvcreate -L1G -s -n snap /dev/data/home
Logging initialised at Mon Jan 23 11:37:41 2006
Set umask to 0077
Loaded external locking library liblvm2clusterlock.so
Setting chunksize to 16 sectors.
Finding volume group "data"
Archiving volume group "data" metadata (seqno 112).
Creating logical volume snap
Creating volume group backup "/etc/lvm/backup/data" (seqno 113).
Zeroing start of logical volume "snap"
Error locking on node kain.mediatransfer.de: Internal lvm error, check
syslog
Problem reactivating origin home
Wiping internal VG cache
the logfile says:
device/dev-io.c:456 Closed /dev/sdb1
cluster_locking.c:412 Locking
0kqnkigkyVKpwYzD03xTbAFQdsuqKApjX09CQG8r0oa0gx7SDFu8KcNjZIYs5DZL at 0x1e
cluster_locking.c:360 Error locking on node kain.mediatransfer.de:
Internal lvm error, check syslog
lvcreate.c:776 Problem reactivating origin home
lvcreate.c:814 <backtrace>
cluster_locking.c:412 Locking V_data at 0x6
filters/filter-persistent.c:181 Dumping persistent device cache to
/etc/lvm/.cache
cache/lvmcache.c:574 Wiping internal VG cache
creates a new logical volume without problems works.
any hints?
I use CentOS release 4.2
thanks Falk
reply other threads:[~2006-01-23 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43D4B498.4000306@mediatransfer.com \
--to=f.hackenberger@mediatransfer.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.