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.
DescriptionCorey Marthaler
2011-03-16 22:59:28 UTC
Description of problem:
When a 2-way mirror suffers a leg device failure and it's policy is set to allocate, that mirror is down converted to linear and then up converted back to a 2-way mirror again. During this process, the original log device is removed and replaced even though it didn't fail. LVM should attempt to use that same device if it can since there's a chance the user specified that device specifically during creation.
# Fail the SECONDARY device
# before the failure
[root@taft-01 ~]# lvs -a -o +devices
LV Log Devices
syncd_secondary_2legs_1 syncd_secondary_2legs_1_mlog syncd_secondary_2legs_1_mimage_0(0),syncd_secondary_2legs_1_mimage_1(0)
[syncd_secondary_2legs_1_mimage_0] /dev/sdc1(0)
[syncd_secondary_2legs_1_mimage_1] /dev/sdf1(0)
[syncd_secondary_2legs_1_mlog] /dev/sdg1(0)
# after the failure
[root@taft-01 ~]# lvs -a -o +devices
LV Log Devices
syncd_secondary_2legs_1 syncd_secondary_2legs_1_mlog syncd_secondary_2legs_1_mimage_0(0),syncd_secondary_2legs_1_mimage_1(0)
[syncd_secondary_2legs_1_mimage_0] /dev/sdc1(0)
[syncd_secondary_2legs_1_mimage_1] /dev/sdh1(0)
[syncd_secondary_2legs_1_mlog] /dev/sdb1(0)
# Fail the PRIMARY device
# before the failure
[root@taft-01 ~]# lvs -a -o +devices
LV Log Devices
syncd_primary_2legs_1 syncd_primary_2legs_1_mlog syncd_primary_2legs_1_mimage_0(0),syncd_primary_2legs_1_mimage_1(0)
[syncd_primary_2legs_1_mimage_0] /dev/sdf1(0)
[syncd_primary_2legs_1_mimage_1] /dev/sdh1(0)
[syncd_primary_2legs_1_mlog] /dev/sde1(0)
# after the failure
[root@taft-01 ~]# lvs -a -o +devices
LV Log Devices
syncd_primary_2legs_1 syncd_primary_2legs_1_mlog syncd_primary_2legs_1_mimage_0(0),syncd_primary_2legs_1_mimage_1(0)
[syncd_primary_2legs_1_mimage_0] /dev/sdh1(0)
[syncd_primary_2legs_1_mimage_1] /dev/sdg1(0)
[syncd_primary_2legs_1_mlog] /dev/sdb1(0)
Version-Release number of selected component (if applicable):
2.6.32-94.el6.x86_64
lvm2-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
lvm2-libs-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
lvm2-cluster-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
udev-147-2.31.el6 BUILT: Wed Jan 26 05:39:15 CST 2011
device-mapper-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-libs-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-event-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
device-mapper-event-libs-1.02.62-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
cmirror-2.02.83-2.el6 BUILT: Tue Feb 8 10:10:57 CST 2011
Might be doable, I'm not sure. Jon, please see if the code can easily support this, or if the two steps are completely independent. (Effectively the log needs splitting off into a separate LV instead of deleting, and then the 2nd step needs to accept that pre-existing log as an LV instead of allocating a new one. Could be a cmdline extension like the 'make me a snapshot using this pre-existing cow' one.)
Comment 4Jonathan Earl Brassow
2012-01-04 21:34:32 UTC
Focus will be on "raid1" segment type for the future. Although a nice-to-have feature, the current solution harms no-one and we should be encouraging use of "raid1" not making it easier to stay on a legacy segment type.
Comment 5RHEL Program Management
2012-01-04 21:45:18 UTC
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.