Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 205831

Summary: device-mapper mirror: Bad status line output
Product: Red Hat Enterprise Linux 4 Reporter: Jonathan Earl Brassow <jbrassow>
Component: kernelAssignee: Alasdair Kergon <agk>
Status: CLOSED NEXTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: agk, dwysocha, jbrassow, 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-11-30 16:44:13 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:
Attachments:
Description Flags
Patch to fix status output of device-mapper mirror target none

Description Jonathan Earl Brassow 2006-09-08 20:15:38 UTC 
The device-mapper mirror target is putting out a status string that has trailing
white-space.  This is causing target tables to be loaded multiple times for the
same device during LVM operations like lvconvert and lvrename, because LVM is
doing a simple string comparison.  Loading multiple identical tables causes
serious problems with cluster mirroring especially.

This issue is not severe, as the work-around in user-space is trivial.  However,
it should be fixed in the kernel.  The attached patch is being push upstream.
Comment 1 Jonathan Earl Brassow 2006-09-08 20:15:38 UTC 
Created attachment 135873 [details]
Patch to fix status output of device-mapper mirror target
Comment 2 Jonathan Earl Brassow 2006-11-13 23:04:37 UTC 
There is a work-around in userspace for this in RHEL4.

This has been fixed in RHEL5/upstream.
Comment 3 Jonathan Earl Brassow 2006-11-30 16:44:13 UTC 
Workaround in RHEL4.4
Fix in RHEL 5.0 (and also present upstream)