Bug 210398

Summary: converted mirrors need the rename function as well
Product: Red Hat Enterprise Linux 4 Reporter: Corey Marthaler <cmarthal>
Component: lvm2Assignee: Jonathan Earl Brassow <jbrassow>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: agk, dwysocha, mbroz
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-11 21:25:22 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-10-11 20:40:30 UTC
Description of problem:
RHEL4u4 version of bz 210396

You can rename a "regular" mirror but not a converted mirror.

# Works
[root@link-08 lvm]# lvcreate -n mirror -L 10G vg
  Logical volume "mirror" created
[root@link-08 lvm]# lvrename vg /dev/vg/mirror mirror2
  Renamed "mirror" to "mirror2" in volume group "vg"


# Doesn't work
[root@link-08 lvm]# lvcreate -L 10G -n lv vg
  Logical volume "lv" created
[root@link-08 lvm]# lvconvert -m 1 /dev/vg/lv
  Logical volume lv converted.
[root@link-08 lvm]# lvrename vg /dev/vg/lv mirror2
  Mirrored LV, "lv" cannot be renamed: Function not implemented

Version-Release number of selected component (if applicable):
[root@link-08 lvm]# rpm -q lvm2
lvm2-2.02.06-6.0.RHEL4

Comment 1 Jonathan Earl Brassow 2006-11-30 20:56:06 UTC
Mirrors should not be able to be renamed, no matter how they are created.  I
believe there is an RFE for this though.

[root@neo-06 ~]# lvcreate -m1 -L 500M -n lv vg
  Logical volume "lv" created
[root@neo-06 ~]# lvrename vg lv lv2
  Mirrored LV, "lv" cannot be renamed: Function not implemented
[root@neo-06 ~]# lvrename vg /dev/vg/lv lv2
  Mirrored LV, "lv" cannot be renamed: Function not implemented


Comment 2 Corey Marthaler 2006-12-11 21:25:22 UTC
Jon you're correct. This is not a bug.