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

RE: Rescuing a repository

From: Jan Evert van Grootheest <j.grootheest_at_euronext.nl>
Date: 2004-05-14 13:37:15 CEST

Marc,

You could at least dump the rest of the repository using -r!
You'd only lose one revision.

-- Jan Evert

> -----Original Message-----
> From: Marc Haisenko [SMTP:haisenko@webport.de]
> Sent: Friday, May 14, 2004 1:23 PM
> To: users@subversion.tigris.org; dev@subversion.tigris.org
> Subject: Rescuing a repository
>
> Hi folks,
> we have a big repository (strings file is 3.1GB) on a RAID 5. Problem is,
> I
> can't dump the repository, I always get a checksum mismatch in revision
> 336.
> And it seems the latest revision has the same problem as well.
>
> The system is a SuSE 8.2 with BDB 4.0.14, running SubVersion 0.37 (sic). I
>
> yesterday and today tried to rescue the repository with with SubVersion
> 1.0.2
> linked against BDB 4.1.25, and SubVersion 1.0.2 linked against BDB 4.2.52,
>
> but everything failed.
>
> First, I made a copy the repository so I can't mess up the original. I
> then
> ran SVN 0.37/BDB 4.0.14 'svnadmin recover /export/rescue', which after
> several minutes said "Input/output error" (note that despite the path this
> is
> not a NFS directory). I then copied the copy to check whether there is a
> problem with the RAID or something, but the copy went smooth. A fsck also
> went without problems.
>
> I then ran 'svnadmin dump /export/rescue', and everything went fine until
> it
> reached revision 336 where a checksum mismatch was reported. Repeatedly
> running the dump always yields the exact same checksum mismatch (always
> the
> same checksums).
>
> I suspected a defect RAM, installed Memtest86 and ran it but after letting
> it
> run through the night no defective RAM was found.
>
> Then today I downloaded BDB 4.1.25 and SVN 1.0.2, and compiled/linked SVN
> 1.0.2 against the BDB 4.1.25. Results are the very same as with SVN
> 0.37/BDB
> 4.0.14
>
> I then also downloaded BDB 4.2.52, linked another SVN 1.0.2 against it an
> ran
> its 'svnadmin recover'... this time the recover came back almost
> immediately,
> reporting the correct current revision number (r506). But the dump still
> doesn't work.
>
> What's also interesting is that when trying to dump the revision 336 I get
>
> different checksums for SVN 0.37 and SVN 1.0.2
>
> SVN 0.37/BDB 4.0.14:
> svn: Checksum mismatch on rep '4pi':
> expected: fe339b5a4133f58051f1f15380f46413
> actual: 4d21ea0c68cdde21698bc99e86eab179
>
> SVN 1.0.2/BDB 4.1.25:
> svn: Checksum mismatch on rep '4pi':
> expected: fe339b5a4133f58051f1f15380f46413
> actual: 7fc67fdbf244751f68f229270c97c3de
>
> SVN 1.0.2/BDB 4.2.52:
> svn: Checksum mismatch on rep '4pi':
> expected: fe339b5a4133f58051f1f15380f46413
> actual: 7fc67fdbf244751f68f229270c97c3de
>
> I also tried experimenting with 'db_recover' but the 4.0.14 and 4.1.25
> versions both yield the 'Input/output error'. And the 4.2.52 'db_recover'
> returns immediately, no output whatsoever.
>
> It's very important to get that repository up and running again as my boss
> is
> fed up with SubVersion and will force me to ditch it if I can't get it
> running again... the repository contains our main products.
>
> So can anyone hint me what else I might try ? Or if nothing else works,
> how I
> could possible try to fix that transaction by hand (I don't fear binary
> editors ;-)
>
> Thnx in advance,
> Marc
>
> --
> Marc Haisenko
> Systemspezialist
> Webport IT-Services GmbH
> mailto: haisenko@webport.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
 

 === E U R O N E X T - D I S C L A I M E R =============================

 This e-mail and its attachments are only intended for the individual(s) or
entity(entities) named above to whom they are addressed and may contain
personal and/or confidential information. Please notify us immediately if
you are not the intended recipient. Any dissemination, duplication,
publication to third parties or other use of the contents of this e-mail or
its attachments is forbidden. Although this information has been compiled
with great care, neither Euronext N.V. nor its subsidiaries shall accept any
responsibility for any errors, omissions or other inaccuracies in this
information or for the consequences thereof, nor shall it be bound in any
way by the contents of this e-mail or its attachments. In the event of
incomplete or incorrect transmission please return the e-mail to the sender.

 Cet e-mail et ses annexes sont uniquement destinés à la (aux) personne(s),
ou à l' (aux) entité(s) à laquelle (auxquelle(s)) il est adressé, visée (s)
en tête du présent message. Il peut contenir des informations personnelles
ou confidentielles. Merci de nous notifier immédiatement si cet e-mail vous
a été adressé par erreur. Toute diffusion, copie, publication à des tiers ou
toute autre utilisation de son contenu est interdite. Bien que cette
information ait été rassemblée avec une grande attention, ni Euronext N.V.
ni aucune de ses filiales, ne peut être tenue responsable des erreurs,
omissions ou inexactitudes contenues dans cette information, ni ne peut être
liée d'aucune manière par le contenu de cet e-mail ou ses annexes. En cas de
transmission incorrecte ou incomplète, nous vous prions de retourner cet
e-mail à son émetteur.

 Deze e-mail en zijn bijlagen zijn uitsluitend bestemd voor de
geadresseerde(n) als op dit e-mailblad vermeld. Het is mogelijk dat deze
e-mail persoonlijke en/of vertrouwelijke informatie bevat. Wanneer u niet de
geadresseerde bent, verzoeken wij u dringend ons daarvan te berichten. Elke
verspreiding, vermenigvuldiging, gebruik of openbaarmaking aan derden van de
inhoud van deze e-mail en zijn bijlagen, is verboden. Hoewel deze informatie
met de meeste zorg is samengesteld is Euronext N.V., en de tot Euronext N.V.
behorende werkmaatschappijen, op geen enkele wijze aansprakelijk voor
eventuele fouten, omissies of andere onjuistheden in deze informatie of de
gevolgen daarvan noch op enigerlei wijze gebonden aan de inhoud van de
e-mail of zijn bijlagen. Gelieve, in geval van onjuiste of onvolledige
ontvangst, deze e-mail terug te sturen naar de afzender.

 ================================

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 15 05:28:06 2004

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