All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladislav Bogdanov <bubble@hoster-ok.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] clvm, snapshots and live migration
Date: Sun, 27 Nov 2011 11:44:06 +0300	[thread overview]
Message-ID: <4ED1F856.6070505@hoster-ok.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F753EC9E8C0@lisa.maurer-it.com>

Hi,

24.11.2011 13:42, Dietmar Maurer wrote:
> Hi all,
> 
> We use clvm and store VM images on shared storage, and our backup tool uses LVM snapshots,
> which seems to require that we exclusively lock the LVs.
> 
> But live migration requires that we activate the LVs on two nodes, so this conflicts with exclusive locks.
> 
> So is there a way to convert the exclusive lock into a local lock. I get an error when try that.
> 
> For example:
> 
> First acquire an exclusive lock:
> # lvchange -aey vmdisks/vm-102-disk-1
> 
> I now want to change that into an local lock:
> 
> # lvchange -aly vmdisks/vm-102-disk-1 
>   Error locking on node proxmox-7-60: Device or resource busy
> 
> Is there a way to do that? What is the reasoning behind not allowing that?

Not actually an answer.
After migration you'd need to convert lock opposite way.
One problem I see here is that if we upgrade local lock to exclusive,
then we need either to force other nodes to drop their local lock unless
LV is used or just fail.

Probably lvm list is a better place for such discussions?

Vladislav



  reply	other threads:[~2011-11-27  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 10:42 [Cluster-devel] clvm, snapshots and live migration Dietmar Maurer
2011-11-27  8:44 ` Vladislav Bogdanov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-28  6:20 Dietmar Maurer

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=4ED1F856.6070505@hoster-ok.com \
    --to=bubble@hoster-ok.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.