Bug 162607
| Summary: | pvmove could use a better error message when it's unable to activate an lv for exclusive locking | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
| Component: | lvm2 | Assignee: | Christine Caulfield <ccaulfie> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.4 | CC: | agk, ccaulfie, dwysocha, jbrassow, mbroz |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2007-0287 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-05-07 23:56:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Related to bug 162809 Firstly, similar to the other one - can we find a form of words in cluster_locking.c that covers all these cases better? (May also need special handling in pvmove itself) This is the message currently generated: # pvmove /dev/dm-3 Error locking on node bench-13.lab.msp.redhat.com: Volume is busy on another node Failed to activate test will that do ? fix verified in lvm2-cluster-2.02.13-1, lvm2-2.02.13-1. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0287.html |
Description of problem: Currently if an lv is active and mounted on other nodes when attempting a pvmove, the pvmove will fail: [root@link-02 ~]# pvmove -v /dev/sda1 /dev/sda7 Loaded external locking library liblvm2clusterlock.so Finding volume group "linear_8_2048" Archiving volume group "linear_8_2048" metadata. Creating logical volume pvmove0 Moving 75 extents of logical volume linear_8_2048/linear_8_20480 Error locking on node link-02: Resource temporarily unavailable Failed to activate linear_8_20480 It would be nice if it said that it was unable to grant exclusive access, and to make sure that it's not being used on other nodes. Version-Release number of selected component (if applicable): Cluster LVM daemon version: 2.01.09 (2005-04-04) Protocol version: 0.2.1 How reproducible: everytime