On 2005-03-19T18:19:44, "Peter T. Breuer" <[EMAIL PROTECTED]> wrote:
> > That part is really simple in theory. > > Knowing which blocks are/may be different does not help them decide who is > _right_. > > Lars, I am trying to move you "upwards" from the detail of the > algorithms to a level at which you can see that there is no algorithm > that can decide reliably which of two diverged traces is the more > "valid" in some sense. As I've said, there's a variety of decision algorithms; that already implied there's no one answer, but always a trade-off. And sometimes, the admin might have to make the choice and manually add the changes made to one set to the other. > > Wrong model. They know that at one point in time they've been in sync, > > and that they have since diverged, and so they can figure out where > > those differences occur. > They can't. That's the point. See above rough hack at a proof. You're mixing this up. The mail I replied to said they can't figure out what happened; that they can. Is there a perfect conflict resolution algorithm which preserved all changed and merged them perfectly? Probably not; not at the block layer, in any case. I never claimed that; see above. Please, keep your argument straight. -- High Availability & Clustering SUSE Labs, Research and Development SUSE LINUX Products GmbH - A Novell Business - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
