[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

relation to minfo-cnt bug Re: predecessor count for the root node-revision is wrong message

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Wed, 21 Mar 2012 10:39:14 +0200

Jason,

I've learnt yesterday something new about the minfo-cnt corruption bug:
it can manifest not only as absurdly high values (on the order of 2**70),
but as far smaller wrong increments too (such as increment of 172
instead of of 0 on one occasion).

Could you determine whether said bug has occurred in your history? You
can do that by duplicating your repository using svnsync or dump|load,
running dump-noderev.pl on / of both copies at the same revisions, and
comparing the minfo-cnt values.

I would be interested in knowing whether they are equal between the two
copies.

Thanks,

Daniel

Jason Wong wrote on Thu, Feb 16, 2012 at 11:42:42 -0800:
> > ./dump-noderev.pl /repository / 61851
> ------------------------------
>
> id: 0.0.r61851/33470
> type: dir
> pred: 0.0.r61850/3844
> count: 61818
> text: 61851 32225 1232 1232 7555349571e297c23e647cc2441d5b8f
> cpath: /
> copyroot: 0 /
> minfo-cnt: 25685
> ------------------------------
Received on 2012-03-21 09:39:57 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.