On Tue, Mar 15, 2011 at 10:44 AM, ankush chadha
<ankushchadha2003_at_yahoo.com>wrote:
> Try running following commands to grab info about r607 on the server side
>
> svn info file:///<Path_To_Repository> -r 607
>
> svn log file:///<Path_To_Repository> -r 607
>
>
C:\Documents and Settings\julesh>svn info
https://svn.knowledgextensions.com/svn
-r 607
Path: svn
URL: https://svn.knowledgextensions.com/svn
Repository Root: https://svn.knowledgextensions.com/svn
Repository UUID: cd97b3e7-f46f-2e48-baaf-a76abbe1cd95
Revision: 607
Node Kind: directory
Last Changed Author: andyg
Last Changed Rev: 607
Last Changed Date: 2007-11-01 17:38:57 -0400 (Thu, 01 Nov 2007)
C:\Documents and Settings\julesh>svn log
https://svn.knowledgextensions.com/svn
-r 607
------------------------------------------------------------------------
r607 | andyg | 2007-11-01 17:38:57 -0400 (Thu, 01 Nov 2007) | 1 line
------------------------------------------------------------------------
C:\Documents and Settings\julesh>
>
> Also check if 607 file is located under following folders
> <Path_To_Repository>\db\revs
> <Path_To_Repository>\db\revprops
>
>
Both exist
> hotcopy is another option to restore the svn repository. I have used
> svnadmin dump before but never faced this problem. Make sure that you are
> using same version of binaries throughout.
>
>
hotcopy completed, failure with snvadmin verify on revision 607 in both the
old repository and and the newly created hotcopied repository.
I'm at a loss. What can I do next?
> You should also mirror your svn repository to reduce downtime and
> surprises.
>
>
>
Thats all well and good unless your mirror is corrupted too.
Thanks
jules
------------------------------
> *From:* Jules Herr <jherr_at_inmedius.com>
> *To:* ankush chadha <ankushchadha2003_at_yahoo.com>
> *Cc:* users_at_subversion.apache.org
> *Sent:* Mon, March 14, 2011 1:48:25 PM
> *Subject:* Re: Failed SVN Verify Logs
>
> Yes we're using the binaries for Collabnet, not exactly sure which version
> it is - is there an easy way to determine?
>
> Not sure if I can access revision 607, is there a way to determine what
> files are in a particular revision?
>
> It appears I can run verification on all revisions 1-606 and I'm running a
> verify on 608-8968 right now, seems to be running OK.
>
> Users have had no problems accessing the repository, and this problem has
> only made itself evident since we've tried to move our SVN repo via dump
> files to a new server.
>
> I'm currently attempting a hot-copy as this has apparently fixed another
> users repo who was experiencing similar symptoms:
>
>
> http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup
>
>
> <http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup>
> Thanks
> jules
>
>
>
>
> On Mon, Mar 14, 2011 at 1:39 PM, ankush chadha <ankushchadha2003_at_yahoo.com
> > wrote:
>
>> Which subversion binaries are you using? Are these the ones from
>> Collabnet?
>>
>> Can you access revision 607? Can you also try resuming the verification
>> process from revision 607?
>>
>> Ankush
>>
>>
>> ------------------------------
>> *From:* Jules Herr <jherr_at_inmedius.com>
>> *To:* users_at_subversion.apache.org
>> *Sent:* Mon, March 14, 2011 10:42:16 AM
>> *Subject:* Failed SVN Verify Logs
>>
>> Hi,
>>
>> I had a failed SVN VERIFY and am submitting the log files as directed by
>> the application. Any and all help is greatly appreciated!
>>
>> Thanks
>> Jules
>>
>>
>>
>> Here is the screen shot and log files of the svnadmin verify which I did
>> in Windows against the kxsrc Subversion repository
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Jules Herr
>> Technology Solutions Provider
>> jherr_at_inmedius.com
>> skpe: jules.herr
>>
>>
>>
>>
>
>
> --
>
> Jules Herr
> Technology Solutions Provider
> jherr_at_inmedius.com
> skpe: jules.herr
>
>
>
>
Received on 2011-03-16 00:39:17 CET