Bug 250658 - when lvchange fails on an active mirror, the error code should be non zero
when lvchange fails on an active mirror, the error code should be non zero
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2 (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Milan Broz
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2007-08-02 15:03 EDT by Corey Marthaler
Modified: 2013-02-28 23:05 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 16:47:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0179 normal SHIPPED_LIVE lvm2 bug-fix and enhancement update 2009-01-20 11:05:45 EST

  None (edit)
Description Corey Marthaler 2007-08-02 15:03:08 EDT
Description of problem:
[root@link-08 ~]# lvchange -pr mirror_1_3859/mirror_1_38590
  Cannot change permissions of mirror "mirror_1_38590" while active.
[root@link-08 ~]# echo $?

Version-Release number of selected component (if applicable):
Comment 1 Corey Marthaler 2007-08-15 09:34:27 EDT
This should probably be an lvm2 bug, not lvm2-cluster.
Comment 2 Milan Broz 2008-06-17 10:07:04 EDT
And that's only for cluster mirror, local mirror works fine...
Comment 4 RHEL Product and Program Management 2008-07-31 09:20:40 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 5 Milan Broz 2008-09-19 07:11:27 EDT
In lvm2-2.02.40-1.el5.
Comment 8 errata-xmlrpc 2009-01-20 16:47:03 EST
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 therefore 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.


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