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

Re: corrupt file

From: Johnathan Gifford <jgifford_at_wernervas.com>
Date: 2006-10-18 17:32:31 CEST

We had the same problem. We also tried John's script as well. Didn't
work. We eventually sent our repository off to CollabNet through our
support contract and they repaired the corrupted revisions. Not sure
what CpllabNet did or used to fix the problem, but they did fix it.
Guess that is why we paid the big bucks for the support we did.

If you don't have a CollabNet or Polarion support contract or can't
purchase one, you may be out of luck in resolving this. This is the
first time in almost less than a year I'm glad we had our support
contract with CollabNet. Definitely worth considering if your
repositories are important.

As a reminder to everyone, run 'svnadmin verify' at least weekly if not
daily on your repositories. You don't want to find out you had a
problem five months ago. Someone posted a simple shell script to cycle
through all the repositories a while back. It is definitely a good
start for a cron script.

Johnathan

>>> On Wed, Oct 18, 2006 at 9:58 AM, in message
<A328BE1531DB8543B7C4ADF55C4298FC077453@VM-UTVEX01.utvikling.mattilsynet.no>,
"Kristian Berre" <Kristian.Berre@mattilsynet.no> wrote:
> I have tried the script posted on
> http://subversion.tigris.org/issues/show_bug.cgi?id=2467, but still
have
> problems. When I run the script with no options I get:
>
> NodeRev Id: uc.0.r9/1598131
> type: file
> text: INVALID 9 1385989 1244 2640 4e8c272e56a9dbed600f25c5e1bbb4ef
> cpath:
> /fagsystem/matsys/trunk/mt-
client/src/main/java/com/computas/mt/ui/virks
> omhet/VirksomhetHeadingVC.java
> copyroot: 0 /
> Invalid rep header found at 1385989 ( )!
> Found problem in NodeRev uc.0.r9/1598131 (1598131)
> text: INVALID 9 1385989 1244 2640 4e8c272e56a9dbed600f25c5e1bbb4ef
> At offset 1385989
>
> After I run the script with - f and run it again with no option I
get:
>
>
> NodeRev Id: uc.0.r9/1598131
> type: file
> text: DELTA 9 1385989 1244 2640 4e8c272e56a9dbed600f25c5e1bbb4ef
> cpath:
> /fagsystem/matsys/trunk/mt-
client/src/main/java/com/computas/mt/ui/virks
> omhet/VirksomhetHeadingVC.java
> copyroot: 0 /
> starting length: 1240
> offset: 1385995
> size > length
> size: 5
> length: 3
> total: 1237
> remaining: 3
> Traceback (most recent call last):
> File "./fsfsverify.py", line 684, in ?
> process(noderev, rev_file, options.dump_instructions,
> options.dump_windows)
> File "./fsfsverify.py", line 637, in verify
> dump_windows)
> File "./fsfsverify.py", line 274, in verify
> digest = parse_svndiff(f, self.length, dump_instructions,
> dump_windows)
> File "./fsfsverify.py", line 191, in parse_svndiff
> raise "error"
> error
>
> When I run: svnadmin dump repo - r9
> I get: svnadmin: Reading one svndiff window read beyond the end of
the
> representation
>
> Does anyone know how to fix this?
>
> Before the fix I got this error when checking out:
>
> Error Can't read length line in file '/var/svn/repos/db/revs/9'
>
> After the fix I get a checksum mismatch while reading
representation.
>
> We are running version 1.3.2 on redhat.
>
> We are about to go into production so we are wondering if we have to
> switch to cvs, but with 1400 revisions we don't want to if don'e
have
> to.
>
> Does anyone know if the problem less likely to occur in 1.4?
>
>
> Any help would be appreciated.
>
> Best Regards
> Kristian Berre
>
>
---------------------------------------------------------------------
> To unsubscribe, e- mail: users- unsubscribe@subversion.tigris.org
> For additional commands, e- mail: users- help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 18 17:35:41 2006

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.