From: Rob <lists@rarforge.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM snapshot with Clustered VG
Date: Thu, 03 Jan 2013 18:56:47 -0800 [thread overview]
Message-ID: <50E644EF.6060209@rarforge.com> (raw)
Is there a way to convert an active LV on a clustered VG to an exclusive
lock without deactivating it first? Or some way of taking a snapshot of
a clustered LVM? I know I have read snapshots are not possible on CLVM,
but the information seems outdated.
ha node1: /dev/vg_clus/logvol_clus
ha node2: /dev/vg_clus/logvol_clus
1) I can deactivate the the entire vg on node1 and node2 with 'vgchange
-an vg_clus' and activate with -ay. Just stating cluster vg is working.
2) I can deactivate locally on node2 with 'vgchange -aln vg_clus' , it
shows inactive on node2 and active still on node1
- After deactivating, I cannot get exclusive lock on node1 with
'vgchange -aey vg_clus'
I get an error locking on node1
3) I can get exclusive an lock if I deactivate the VG on both nodes and
then run 'vgchange -aey vg_clus' on either node. The lvcreate snapshop
works, but again, it requires deactivating the vg, which isn't an option
in production.
Setup:
Centos 6.3 (current)
cman+pacemaker dual primary drbd for HA KVM w/ live migration
disk: lvm -> drbd -> clvm -> kvm virt
Currently I am taking a lvm snapshot of the drbd lvm backing device, but
it's not ideal ( as there are other issues )
Thanks for the time!
-Rob
next reply other threads:[~2013-01-04 2:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 2:56 Rob [this message]
2013-01-04 5:38 ` [linux-lvm] LVM snapshot with Clustered VG Vladislav Bogdanov
-- strict thread matches above, loose matches on Subject: below --
2013-03-01 11:28 Andreas Pflug
2013-03-01 15:41 ` Vladislav Bogdanov
2013-03-06 7:40 ` Andreas Pflug
2013-03-06 7:58 ` Vladislav Bogdanov
2013-03-06 9:15 ` Andreas Pflug
2013-03-06 9:35 ` Vladislav Bogdanov
2013-03-06 9:59 ` Andreas Pflug
2013-03-06 11:20 ` Vladislav Bogdanov
2013-03-06 12:17 ` Andreas Pflug
2013-03-06 13:28 ` Vladislav Bogdanov
2013-03-12 6:52 ` Andreas Pflug
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=50E644EF.6060209@rarforge.com \
--to=lists@rarforge.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).