Daniel Shahaf wrote on Tue, Feb 28, 2012 at 07:17:04 +0200: > Stefan Sperling wrote on Tue, Feb 28, 2012 at 03:18:35 +0100: > > On Mon, Feb 27, 2012 at 03:25:00PM -0800, Jason Wong wrote: > > > I guess I am wondering that if this is the case, then why is it that > > > if the check-in fails, and then we manually check it in again using > > > tortoisesvn, that it works the second time? > > > > As far as I know, we don't know what the underlying problem is yet. > > So I'm afraid I cannot answer all of your questions in a satisfactory > > manner because I don't know the answers. > > I'm not really surprised by this situation. I guess Jason means "the > same set of tree/text/prop/revprop changes" when he says "it", but by > the nature of the bug it may well have to do with some concurrency > issues on the server --- i.e., it depends on more than just the contents > being committed. > > > Daniel might know more -- he has been following the problem more closely > > than me. And I hope he will correct me if I'm making any wrong or > > misleading statements in this post :) > > Yeah, I'm following this thread :) > > > > We have been using svn for a while now and I am > > > wondering what this means that for 1.6, that this issue has been > > > occurring from communcations between 1.6 client and 1.6 server. > > > > It has probably been happening since before the 1.7 release. > > The problem was first discovered in the ASF repository. The first > > occurrence there has been traced to a time before 1.7.0 was released. > > At the time the ASF server was still running 1.6, and the first commit > > that introduced the problem in the ASF repository was very likely > > a 1.6 client. > > > > AI We should check whether it _was_ a 1.6 client.. > > > > Also, is this bug something that svnadmin verify will not detect? > > > The last time we ran svnadmin verify, it said all was good. > > > > Apparently, svnadmin verify won't find it. > > This should probably be fixed. But the priority right now is to > > understand why it is happening in the first place. > > > > AI The 'verify' part is a relatively low-hanging fruit, though. >
Done: r1294479 and followups. See also r1294470 which improves the error message. The latter will hopefully be in 1.7.4. svn_fs_verify() is not present in 1.7.x so the r1294479 set of changes cannot easily be backported. > AI File an issue for the pred-count bug Issue #4129: http://subversion.tigris.org/issues/show_bug.cgi?id=4129