Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 238031

Summary:	cluster mirrors not handling all recovery/write conflicts
Product:	[Retired] Red Hat Cluster Suite	Reporter:	Jonathan Earl Brassow <jbrassow>
Component:	cmirror	Assignee:	Jonathan Earl Brassow <jbrassow>
Status:	CLOSED WORKSFORME	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	agk, dwysocha, jbrassow, mbroz, prockai
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:	2008-07-01 14:43:50 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:

Description Jonathan Earl Brassow 2007-04-26 16:27:54 UTC

Problem is that the kernel (main mirror code) does not do any marks/clears when
writing to a region before its recovery.  So, it is not possible for the server
to detect a conflict.  Basically, we must turn back on the
'is_remote_recovering' function and disallow any writes to regions that are OR
WILL BE recovering.

It's really going to cause some pain during writes while mirrors are re-syncing.
 We might be able to find a better fix for 4.6.

Comment 1 Jonathan Earl Brassow 2007-04-26 17:08:52 UTC

assigned -> post

Comment 2 Jonathan Earl Brassow 2007-08-22 17:34:37 UTC

this issue was resolved in 4.5, and the "better fix" is in place for 4.6.

post -> modified.

Comment 3 Corey Marthaler 2008-07-01 14:43:50 UTC

Closing this bug.