Bug 820229
| Summary: | fail to rename the thin LV | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Peter Rajnoha <prajnoha> |
| Component: | lvm2 | Assignee: | Zdenek Kabelac <zkabelac> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3 | CC: | agk, bmarzins, bmr, cb20777, cmarthal, dwysocha, heinzm, jbrassow, jonathan, lvm-team, mbroz, msnitzer, nperic, prajnoha, prockai, thornber, xiaoli, zkabelac |
| Target Milestone: | rc | ||
| Target Release: | 6.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.97-2.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Attempting to rename Logical Volumes gave the following error:
lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name>
This is fixed.
|
Story Points: | --- |
| Clone Of: | 818020 | Environment: | |
| Last Closed: | 2013-02-21 08:09:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 818020 | ||
| Bug Blocks: | |||
|
Description
Peter Rajnoha
2012-05-09 12:40:33 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
It's not possible to rename thin logical volumes using current LVM2 release. The rename ends up with an error "lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name>". This issue will be fixed in next LVM2 release.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1,5 @@
-It's not possible to rename thin logical volumes using current LVM2 release. The rename ends up with an error "lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name>". This issue will be fixed in next LVM2 release.+It is not possible to rename thin logical volumes using tools provided in the current LVM2 release. The rename operation returns the following error:
+
+lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name>
+
+This issue will be fixed in the next LVM2 release.
Deleted Technical Notes Contents. Old Contents: It is not possible to rename thin logical volumes using tools provided in the current LVM2 release. The rename operation returns the following error: lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name> This issue will be fixed in the next LVM2 release.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Attempting to rename Logical Volumes gave the following error:
lvrename Cannot rename <volume_name>: name format not recognized for internal LV <pool_name>
This is fixed.
Adding QA ack for 6.4. Tested and lvrename successfully renamed thin_lv with version 97-2: (09:38:48) [root@r6-node01:~]$ lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert lv_root VolGroup -wi-ao-- 6.54g lv_swap VolGroup -wi-ao-- 1.97g my_log myvg Vwi-a-tz 1.00g thinpool 0.00 thinpool myvg twi-a-tz 1.00g 0.00 (09:38:59) [root@r6-node01:~]$ lvrename myvg my_log your_log WARNING: Thin pool target does not support discards (needs kernel >= 3.4). Renamed "my_log" to "your_log" in volume group "myvg" (09:39:24) [root@r6-node01:~]$ lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert lv_root VolGroup -wi-ao-- 6.54g lv_swap VolGroup -wi-ao-- 1.97g thinpool myvg twi-a-tz 1.00g 0.00 your_log myvg Vwi-a-tz 1.00g thinpool 0.00 Version used: lvm2-2.02.97-2.el6.x86_64 device-mapper-1.02.76-2.el6.x86_64 *** Bug 880331 has been marked as a duplicate of this bug. *** Any idea when this fix (lvm2-2.02.97) will be pushed to the RHEL 6.3 and Fedora-17 updates (or even testing). I don't see it there, but that may be due to bad looking skills on my part. The fix will be in RHEL6.4. It will not be available in 6.3. It should already be in Fedora 18. We'd no immediate plans to put it into F17 updates, but that could be done. 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-2013-0501.html |