Hide Forgot
Description of problem: When trying to deactivate a LV which is currently inactive on a single hsoted server (not clustered environment), the error displayed is ambiguous. Version-Release number of selected component (if applicable): lvm2-2.02.108-1.el6.x86_64 How reproducible: Everytime Steps to Reproduce: [root@tardis-01 ~]# lvchange -aln multi/snap_of_simple Change of snapshot snap_of_simple will also change its origin simple. Proceed? [y/n]: y Cannot deactivate remotely exclusive device locally. Actual results: LVM complains that it cannot deactivate REMOTELY exclusive device when there is not remote server existing. It is confusing. Expected results: LVM should report that the mentioned LV is already inactive and thus cannot be deactivated again.
Just missing check whether the VG is clustered or not - the check doesn't make sense in case it's not clustered. Patched with: https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=c52c9a1e316b6a92a2475dfe3ad2aac92edc80c0
[root@tardis-01 ~]# lvchange -aln new_vg/snap_of_simple Change of snapshot snap_of_simple will also change its origin simple. Proceed? [y/n]: y [root@tardis-01 ~]# Marking VERIFIED with: lvm2-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 lvm2-libs-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 lvm2-cluster-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 udev-147-2.57.el6 BUILT: Thu Jul 24 15:48:47 CEST 2014 device-mapper-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-libs-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-event-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-event-libs-1.02.88-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014 device-mapper-persistent-data-0.3.2-1.el6 BUILT: Fri Apr 4 15:43:06 CEST 2014 cmirror-2.02.109-2.el6 BUILT: Tue Aug 19 16:32:25 CEST 2014
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1387.html