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.

Bug 1508914

Summary:	filesystem corruption if lvchange while raid1 conversion active [rhel-6.9.z]
Product:	Red Hat Enterprise Linux 6	Reporter:	Oneata Mircea Teodor <toneata>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
lvm2 sub component:	Changing Logical Volumes (RHEL6)	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	high	CC:	agk, cmarthal, fche, fweimer, heinzm, igkioka, jbrassow, jmagrini, mcsontos, mjuricek, msnitzer, mthacker, prajnoha, prockai, toneata, zkabelac
Version:	6.9	Keywords:	ZStream
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	lvm2-2.02.143-12.el6_9.1	Doc Type:	Bug Fix
Doc Text:	Due to a missing check, the "lvchange" command allowed setting the primary leg as write-mostly, even when the RAID1 logical volume was not in synchronization. As a consequence, the file system was corrupted. With this update, the required check has been added, and the described problem no longer occurs.	Story Points:	---
Clone Of:	1484110	Environment:
Last Closed:	2017-11-14 21:01:31 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:
Bug Depends On:	1484110
Bug Blocks:

Description Oneata Mircea Teodor 2017-11-02 13:48:01 UTC

This bug has been copied from bug #1484110 and has been proposed to be backported to 6.9 z-stream (EUS).

Comment 5 errata-xmlrpc 2017-11-14 21:01:31 UTC

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.

https://access.redhat.com/errata/RHBA-2017:3209