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

RE: bug? corrupted revision?

From: Andersen, Krista <Krista.Andersen_at_itg.com>
Date: Tue, 28 Jun 2011 21:18:16 -0400

The checkout also failed:
REPORT of '/repos/!svn/vcc/default': Could not read chunk size: connection was
closed by server (http://server)

From: Andersen, Krista
Sent: Tuesday, June 28, 2011 4:48 PM
To: users_at_subversion.apache.org
Cc: Andersen, Krista
Subject: bug? corrupted revision?

Hi SVN users

I found a new error - (at least new to me):
....svnsync: REPORT of 'http://server/repo': Could not read chunk size: connection was closed by server (http://server)

We have the standard master/mirror repo setup as described in the Red Bean book. The sync is kicked off by the post-commit hook script. Today we noticed the sync was stuck on rev 768 on this repo (oddly it was 3 revs behind by then) so I gave the usual svnsync sync command and after a few rows of "....." I got the error posted above.

We recently (within a month or two) upgraded our Sparc-Solaris svn servers from SVN 1.6.9 to 1.6.16.

Usually we don't have sync issues with our many repos but revisions where the revs/?/?? file is near 100M or more does seem to timeout somewhere and we have a workaround that involves a dump/load of the overly large revision. (The file /Svn/repos/db/revs/0/768 is only 44M) I tried to create an incremental dumpfile for this revision 768 but I get another odd error:
[]> svnadmin dump /Svn/repos -r768 --incremental --deltas > dmp768
svnadmin: Can't read file '/Svn/repos/db/revs/0/361': End of file found

Yet oddly - the revision before and after 768 work just fine for creating a dumpfile:
[]> svnadmin dump /Svn/repos -r767 --incremental --deltas > dmp767
* Dumped revision 767.

[]> svnadmin dump /Svn/repos -r769 --incremental --deltas > dmp769
* Dumped revision 769.

The actions of revision 768 was the addition of a completely new folder to the trunk and contents for that folder. There is no relation between 768 and anything that existed in history in revision 361 or any other revision.

I did a svnadmin verify and it was fine until it got to rev 768 - but it complained about rev 361:
[]> svnadmin verify /Svn/repos
* Verified revision 0.
* Verified revision 1.
* Verified revision 359.
* Verified revision 360.
* Verified revision 361.
* Verified revision 362.
* Verified revision 363.
* Verified revision 765.
* Verified revision 766.
* Verified revision 767.
svnadmin: Can't read file '/Svn/repos/db/revs/0/361': End of file found

**Note** there are actually 770 revisions on this repo - but the 'verify' operation died on rev768 - while complaining of rev361.

I'm attempting to run a checkout of this repos' trunk directory to see what happens, (using TortoiseSVN). So far so good, but it is a very large repo and checkouts tend to run overnight. I'll follow up with those results in the morning.

In the meantime - what's up with my repo rev768? Is the repo salvageable?


This message is for the named person's use only. This communication is for
informational purposes only and has been obtained from sources believed to
be reliable, but it is not necessarily complete and its accuracy cannot be
guaranteed. It is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation of any
transaction. Moreover, this material should not be construed to contain any
recommendation regarding, or opinion concerning, any security. It may
contain confidential, proprietary or legally privileged information. No
confidentiality or privilege is waived or lost by any mistransmission. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and notify the
sender. You must not, directly or indirectly, use, disclose, distribute,
print, or copy any part of this message if you are not the intended
recipient. Any views expressed in this message are those of the individual
sender, except where the message states otherwise and the sender is
authorized to state them to be the views of any such entity.

Securities products and services provided to Canadian investors are offered
by ITG Canada Corp. (member CIPF and IIROC - Investment Industry Regulatory
Organization of Canada), an affiliate of Investment
Technology Group, Inc.

Investment research products and services are produced and offered by
ITG Investment Research, Inc. and not ITG Inc. (a FINRA member firm and
SIPC member).

ITG Inc. and/or its affiliates reserves the right to monitor and archive
all electronic communications through its network.

Received on 2011-06-29 03:18:54 CEST

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.