I have investigated the possibility to backport the fix for this issue from trusty (14.04). There has been a major refactoring of the locking all over lvm between versions shipped with precise (2.02.66 patched to 2.02.72) and trusty (2.02.98).
The scope of backporting makes this operation risky and since there is a workaround available the risk would be larger than benefit. Hence, this is a won't fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1383905 Title: pvmove fails while clvm is in use (Device or resource busy) Status in “lvm2” package in Ubuntu: New Bug description: 1. Affected release: precise (12.04) 2. Affected version: clvm 2.02.66-4ubuntu7.4 3. Steps to reproduce: a Setup: * SAN server serving 3 drives * Cluster consisting of 2 nodes b. Connect drives to the cluster (open-iscsi) c. Configure clvm. d. Create PV on all 3 drives. Create clustered VG consisting of 2 of those drives. e. Create LV with size > 10GB f. Create a file on the LV utilizing more space that the size of 1 PV. g. Extend the VG with the 3rd drive. h. pvmove on one of the first two drives. 4. What you expected to happen pvmove succeeds freeing the first selected drive for later removal with vgreduce. 5. What happened instead: sudo pvmove -v /dev/sdc Finding volume group "vg0" Executing: /sbin/modprobe dm-log-clustered FATAL: Module dm_log_clustered not found. /sbin/modprobe failed: 1 Detected pvmove in progress for /dev/sdc Error locking on node server1: Device or resource busy Failed to activate lv0 6. Other information: this issue does not affect trusty (and later) release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1383905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
