Bug 162809

Summary: vgchange -ae error could be much better if vg is already in use
Product: Red Hat Enterprise Linux 4 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 4.4CC: 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:57:25 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:

Description Corey Marthaler 2005-07-08 20:55:17 UTC 
Description of problem:
If I try and grab exclusive "ownership" of a vg for a machine, but that vg is
already in use or exclusive somewhere else, I get an error saying:
"Error locking on node <hostname>: Resource temporarily unavailable".
It should say something like, "VG is already activated else where, please
deactivate if you want to have exclusive access".
Comment 3 Alasdair Kergon 2006-02-01 15:15:43 UTC 
Related to bug 162607.
Comment 6 Christine Caulfield 2006-10-19 08:49:22 UTC 
This is what's currently in CVS:

# lvchange -ay vg/test
  Error locking on node bench-13.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-12.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-18.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-14.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-16.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-15.lab.msp.redhat.com: Volume is busy on another node
  Error locking on node bench-19.lab.msp.redhat.com: Volume is busy on another node
Comment 7 Corey Marthaler 2006-11-01 17:26:50 UTC 
new message verified.
Comment 11 Red Hat Bugzilla 2007-05-07 23:57:26 UTC 
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