Bug 162607 - pvmove could use a better error message when it's unable to activate an lv for exclusive locking
pvmove could use a better error message when it's unable to activate an lv fo...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: lvm2 (Show other bugs)
4.4
All Linux
low Severity medium
: ---
: ---
Assigned To: Christine Caulfield
Cluster QE
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-06 16:17 EDT by Corey Marthaler
Modified: 2007-11-16 20:14 EST (History)
5 users (show)

See Also:
Fixed In Version: RHBA-2007-0287
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-07 19:56:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Corey Marthaler 2005-07-06 16:17:33 EDT
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
Comment 1 Alasdair Kergon 2006-02-01 10:15:21 EST
Related to bug 162809
Comment 3 Alasdair Kergon 2006-10-18 14:38:03 EDT
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)
Comment 4 Christine Caulfield 2006-10-19 04:36:18 EDT
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 ?
Comment 5 Corey Marthaler 2006-11-01 12:56:36 EST
fix verified in lvm2-cluster-2.02.13-1, lvm2-2.02.13-1.
Comment 9 Red Hat Bugzilla 2007-05-07 19:56:27 EDT
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

Note You need to log in before you can comment on or make changes to this bug.