Re: BK problem

[Larry McVoy <lm@bitmover.com>]

On Fri, May 10, 2002 at 12:58:12PM -0500, Eli Carter wrote:
> Larry McVoy wrote:
> > Hi, we've got a problem in one of Linus' trees and it has started to
> > propagate around.  I need your help to track it down and fix it.
> > Please run the following script on your Linux BK trees and contact
> > me if it tells you to do so.  You can fix up the tree by doing the
> > following (warning: takes lots and lots of CPU time so if you don't
> > need the tree it may well be faster to reclone tomorrow after I finish
> > fixing the trees on bkbits).
> 
> Would you mind giving something of a lay-man's explanation of what went 
> wrong and what that means?  In particular, I'm curious about the 
> propagating part...

The short summary is that two people used Linus' import tools and because
of no error on his part, simply the way things worked out, that caused what
we call "duplicate keys" (a lot like duplicate inodes, a lot like it) when
the trees with the imported patch came together.  I wrote a script to fix
up the trees after the fact and the application of that script went wrong
in Linus' tree but was not noticed until later.  It started showing up as
pull errors and then we tracked it down.

The long explanation would take me too long to do in email, I have 
carpal problems and it would amount to writing a "how BK works" paper
and that's too much for me right now.  If you want to understand the
nitty gritty, we can go to voice and I'll tell you.  So far, talking
doesn't seem to hurt my wrists :)
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm