Bug 238031 - cluster mirrors not handling all recovery/write conflicts
Summary: cluster mirrors not handling all recovery/write conflicts
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: cmirror
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jonathan Earl Brassow
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-26 16:27 UTC by Jonathan Earl Brassow
Modified: 2010-01-12 02:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-07-01 14:43:50 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.