Am 01.03.13 16:41, schrieb Vladislav Bogdanov:
Sorry, forgot to reply to list from the first attempt.
Andreas Pflug <pgadmin@pse-consulting.de> wrote:
Hi Vladislav,
I tried the patch you mentioned in
https://www.redhat.com/archives/linux-lvm/2013-January/msg00006.html ,
but apparently it doesn't work for me. On a locally active LV, I still
get
./lvm lvchange -aey -vvvv vg/locktest
...
Activating logical volume "locktest" exclusively
#activate/dev_manager.c:284 Getting device info for vg-locktest
[LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN]
#ioctl/libdm-iface.c:1724 dm info
LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN
NF [16384] (*1)
#locking/cluster_locking.c:568 Lock held for
oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN, node
7400a8c0 : CR
#activate/activate.c:1067 vg/locktest is active
#locking/cluster_locking.c:508 Locking LV
oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN EX
(LV|NONBLOCK|CLUSTER|LOCAL) (0xdd)
#locking/cluster_locking.c:395 Error locking on node 7400a8c0: Device
or resource busy
Can you give me a hint what to try further?
Regards
Andreas
Hi Andreas,
Lock convertion is only enabled if you pass --force flag.
Also, to upgrade local lock to exclusive one, you need to ensure IIRC that no more node holds local lock.
Hm, tried that as well:
tools/lvm lvchange --force -aey -vvvv vg/locktest
--force changes the error from "resource busy" to "invalid argument":
#lvchange.c:243 Activating logical volume "locktest" exclusively
(forced)
#activate/dev_manager.c:284 Getting device info for vg-locktest
[LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN]
#ioctl/libdm-iface.c:1724 dm info
LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN
NF [16384] (*1)
#locking/cluster_locking.c:568 Lock held for
oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN, node
7400a8c0 : CR
#activate/activate.c:1067 vg/locktest is active
#activate/dev_manager.c:284 Getting device info for vg-locktest
[LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN]
#ioctl/libdm-iface.c:1724 dm info
LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN
NF [16384] (*1)
#activate/activate.c:1067 vg/locktest is active
#activate/dev_manager.c:284 Getting device info for vg-locktest
[LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN]
#ioctl/libdm-iface.c:1724 dm info
LVM-oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN
NF [16384] (*1)
#locking/cluster_locking.c:568 Lock held for
oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN, node
7400a8c0 : CR
#activate/activate.c:1067 vg/locktest is active
#locking/cluster_locking.c:508 Locking LV
oW2W7O2cgWRLUhoVR8qqqQY7wlcYexmWU8y83bGQz9IcnXh3GfXslBN6ziZrC3BN EX
(LV|NONBLOCK|CLUSTER|LOCAL|CONVERT) (0x40dd)
#locking/cluster_locking.c:395 Error locking on node 7400a8c0: Invalid
argument
Regards
Andreas
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
