Ryan Schmidt wrote:
> On Dec 12, 2007, at 08:23, Jef Driesen wrote:
>
>> Ryan Schmidt wrote:
>>> On Dec 12, 2007, at 04:55, Jef Driesen wrote:
>>>> I have a repository with 36 revisions. When I tried to commit
>>>> the 37th revision, the svn aborted with a segmentation fault.
>>>> And now my repository is corrupt. How do I recover it?
>>>>
>>>> It appears that the latest commit has overwritten r29, because
>>>> db/ revprops/29 contains the commit message of that last commit.
>>>> Both db/revprops and db/revs contain 38 files (with numbers 0 to
>>>> 37). But my db/current contains "29 c 2". If I dump the
>>>> repository, the last revision is r29, which contains the changes
>>>> of that last commit.
>>> I think you'll have to recover your db/revs/29, db/revprops/29 and
>>> db/ current files from your backups.
>>> After that, "svnadmin verify" would be a good idea.
>>
>> Unfortunately, my last backup only goes back to r28. All changes
>> after that are very recent and thus not yet included in the backup.
>
> You should really modify your backup strategy so that you make a
> backup of each revision as it is committed to the repository, by
> using the post-commit hook to run "svnadmin dump"
Good idea! I didn't know that was possible.
>> Is it possible to start from r28 and create a new r29 by making the
>> same change again? And then replace the corrupt files with the
>> newly created ones. I'm quite sure that I only created a new branch
>> in r29 and did not modify any other files.
>>
>> svn cp file:///repo/trunk file:///repo/branches/mybranch
>
> I don't know if that would work.
I tried and it doesn't work.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 13 10:05:22 2007