bzr error - KnitCorrupt

[Ralph Douglass]

Is there a way to run a repair of some sort?  I can still get patch 
diffs, but I can't rollback the corrupted patches.  Maybe something like 
a --forced-rollback which would overcome the error and discard the 
busted patches?

Robert Collins wrote:
> On Fri, 2007-08-03 at 16:17 -0400, Ralph Douglass wrote:
>   
>> I'm getting this error when I call bzr log.  It seems that it still 
>> works when I give it a specific revision range that does not include
>> two 
>> revisions (26 and 27), including things after the corrupted
>> revision.  
>> bzr diff -r 26 and bzr diff -r also overlap in all but two lines,
>> which 
>> means that they are suspect.
>>
>> Any thoughts on how to recover from this, other than rebuilding the 
>> repo?   It's a small repo, so that's not a big issue this time, but
>> I've 
>> got much larger stuff that I was about to move, and I'd like to feel 
>> comfortable about that migration.
>>
>> The error:
>> ----------------------------------------------------------------------------------------
>>
>> bzr: ERROR: bzrlib.errors.KnitCorrupt: Knit revisions.knit corrupt: 
>> While reading
>> {production at nyc-lvt-007-20070802224632-ykfvrh54zjoqt3do} 
>> got IOError(Not a gzipped file)
>>     
>
> This has indicated flakey hardware in all cases we've seen so far - the
> data in the .knit which should be a sequence of gzip'd files cat'd to
> each other. We only write references to those hunks after the data has
> been written.
>
> -Rob
>
>
>