From: Andreas Pflug <pgadmin@pse-consulting.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Jacek Konieczny <jajcus@jajcus.net>
Subject: Re: [linux-lvm] resize and snapshots with clvm
Date: Wed, 20 Feb 2013 14:18:23 +0100 [thread overview]
Message-ID: <5124CD1F.1020506@pse-consulting.de> (raw)
In-Reply-To: <20130219145940.411cd271@jajo.eggsoft>
Am 19.02.13 14:59, schrieb Jacek Konieczny:
> On Tue, 19 Feb 2013 14:37:07 +0100
> Andreas Pflug <pgadmin@pse-consulting.de> wrote:
>> What I'm missing is the possibility to resize a LV or taking a
>> snapshot of it while a volume is used on one node. I'd expect this to
>> work on the active node, if the volume is inactive on all other
>> nodes.
> I can confirm this works.
>
>> But when I try that, I get
>> cluster request failed: Invalid argument
>> Failed to suspend <logvol>
> Are you sure you have the volume activated _exclusively_ on the single
> node.
> 'is used on one node' doesn't mean much when any other node is allowed
> to activate the volume at any time.
I would have expected lvm to take that exclusive lock implicitely when
necessary?
>
> When the LV is exclusively activated (lvchange -aey) snapshots should
> work (and they do work for me).
The volume is "lvchange -aly" active on one node and in use there (e.g.
mounted or attached to a VM). If I try to lvchange -aey on that node, I
get "Error locking on node xxxx: Device or resource busy". Apparently
the problem is propagating the activation to exclusive if the device is
busy.
Actually, lock exclusive will even fail if the device is not in use, but
only active locally.
A workaround would probably be to activate the lv exclusively _before_
using it, but then it would be impossible to migrate the vm to another
host later on.
Regards
Andreas
next prev parent reply other threads:[~2013-02-20 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 13:37 [linux-lvm] resize and snapshots with clvm Andreas Pflug
2013-02-19 13:59 ` Jacek Konieczny
2013-02-20 13:18 ` Andreas Pflug [this message]
2013-02-20 13:30 ` Jacek Konieczny
2013-02-20 15:41 ` 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=5124CD1F.1020506@pse-consulting.de \
--to=pgadmin@pse-consulting.de \
--cc=jajcus@jajcus.net \
--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.