On Sep 4, 2007, at 08:47, Kamaraju S Kusumanchi wrote:
> Clemens wrote:
>> I have examined your filenames in db/revs and they seem to be
>> complete
>> (namewise). What does your file
>>
>> db/current
>>
>> contain?
>>
>
> $cat /home/rajulocal/src/repos/db/current
> # This vi
That's clearly busted. How did it get that way? Did you have hard
disk corruption at some point? Do you have hard disk corruption right
now? Do you have backups from which you can restore?
>> I do not know for sure what it should contain, but something around
>>
>> 132 d 1
>>
>> would be a good content perhaps. If it does not contain this
>> contents,
>> perhaps try to modify it and retry svnadmin verify ...
>
> Now when I changed it to
>
> $svnadmin verify /home/rajulocal/src/repos/
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> * Verified revision 3.
> * Verified revision 4.
> * Verified revision 5.
> * Verified revision 6.
> * Verified revision 7.
> .....
> * Verified revision 119.
> * Verified revision 120.
> * Verified revision 121.
> * Verified revision 122.
> * Verified revision 123.
> * Verified revision 124.
> svnadmin: Revision file lacks trailing newline
>
> So it seems now it is working upto revision 124. Any idea how to get
> further?
Do you have a backup of the 124 file you could restore? If not, what
is the contents of the 124 file now? Does it look reasonable (that
is, does it look similar in shape to the content of the previous
revision files that verified correctly)?
Before you go making any other changes to your repository in an
attempt to recover it, please make sure you back up the broken
repository as it is now, in case our recovery attempts break it further.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 4 20:38:28 2007