Bug 213484

Summary: RFE: lvremove man page should mention that LVs need to now be deactivated before deleting
Product: [Retired] Red Hat Cluster Suite Reporter: Corey Marthaler <cmarthal>
Component: lvm2-clusterAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 4CC: agk, dwysocha, jbrassow, mbroz
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2007-0046 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-10 21:07:51 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 2006-11-01 17:22:34 UTC
Description of problem:
This used to work before in the clustered domain, but now we need to deactivate
any clustered volume before it can be deleted. 

[root@link-08 lvm]# lvremove -f /dev/vg/foo
  Error locking on node link-08: Volume is busy on another node
  Can't get exclusive access to volume "foo"

From man page:
OPTIONS
       See lvm(8) for common options.

       -f, --force
              Remove active logical volumes without confirmation.


It should mention now that deactivation is now required.

Version-Release number of selected component (if applicable):
[root@link-08 lvm]# rpm -q lvm2
lvm2-2.02.13-1
[root@link-08 lvm]# rpm -q lvm2-cluster
lvm2-cluster-2.02.13-1

Comment 1 Christine Caulfield 2006-11-06 14:12:01 UTC
Checking in WHATS_NEW;
/cvs/lvm2/LVM2/WHATS_NEW,v  <--  WHATS_NEW
new revision: 1.491; previous revision: 1.490
done
Checking in man/lvremove.8;
/cvs/lvm2/LVM2/man/lvremove.8,v  <--  lvremove.8
new revision: 1.4; previous revision: 1.3
done


Comment 2 Corey Marthaler 2006-11-21 22:00:16 UTC
fix verified in lvm2-cluster-2.02.15-3

Comment 4 Red Hat Bugzilla 2007-05-10 21:07:51 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-0046.html