Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
FYI - the current code does not forget to check when changing an existing LV from non-clustered to clustered regardless of whether or not it's currently active.
[root@taft-01 ~]# lvcreate -L 12M -s taft/clinear
Logical volume "lvol0" created
[root@taft-01 ~]# lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices
LogVol00 VolGroup00 -wi-ao 58.38G /dev/sda2(0)
LogVol01 VolGroup00 -wi-ao 9.75G /dev/sda2(1868)
clinear taft owi-a- 100.00M /dev/sdb1(0)
lvol0 taft swi-a- 12.00M clinear 0.07 /dev/sdc1(0)
[root@taft-01 ~]# vgchange -c y taft
Volume group taft contains snapshots that are not yet supported.
[root@taft-01 ~]# vgchange -an taft
0 logical volume(s) in volume group "taft" now active
[root@taft-01 ~]# vgchange -c y taft
Volume group taft contains snapshots that are not yet supported.
In fact there may even be a bug in here, though I think I've brought up the fact that lvm will activate in single machine mode the same volume on multiple nodes.
[root@taft-01 ~]# vgchange -aye taft
2 logical volume(s) in volume group "taft" now active
[root@taft-01 ~]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
LogVol00 VolGroup00 -wi-ao 58.38G
LogVol01 VolGroup00 -wi-ao 9.75G
clinear taft owi-a- 100.00M
lvol0 taft swi-a- 12.00M clinear 0.07
# here the snap doesn't get activated, but the origin does.
[root@taft-02 ~]# vgchange -aye taft
_get_device_info: device not found
1 logical volume(s) in volume group "taft" now active
[root@taft-02 ~]# lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices
LogVol00 VolGroup00 -wi-ao 58.38G /dev/sda2(0)
LogVol01 VolGroup00 -wi-ao 9.75G /dev/sda2(1868)
clinear taft owi-a- 100.00M /dev/sdb1(0)
lvol0 taft swi--- 12.00M clinear /dev/sdc1(0)
Just a note that bug 694164 (targets not resumed when creating multiple snapshots of mirrors) may be seen when attempting this feature. This may require a note in the docs.
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.
http://rhn.redhat.com/errata/RHBA-2011-0772.html