On Feb 14, 2008, at 14:30, Matthias Siedler wrote:
> Matthias Siedler wrote:
>
>> Ryan Schmidt wrote:
>>
>>> On Feb 8, 2008, at 09:39, Matthias Siedler wrote:
>>>
>>>> due to a server crash, a revs file is missing. We haven't
>>>> recognized this early, but got suddenly some troubles, and I had to
>>>> run some svnadmin verify.
>>>>
>>>> Now we have figured out that a revs file 387 is missing (the props
>>>> file is there), and we are already at revision 634.
>>>>
>>>> Because of the props I know what content has been in there, and I
>>>> can go without it. But is there any chance to get the repository
>>>> working properly at all?
>>>
>>> Can you restore the missing 387 rev file from your backups?
>
>>
>> Unfortunately not, the file is too old and not in the current
>> backups any
>> more.
>
> Any other suggestion?
You could "svnadmin dump" revisions 1 thru 386, and then 388 thru
HEAD. Then "svnadmin load" these two into a new repository. Use "--
ignore-uuid" when loading the first part, so that you'll be sure to
get a new repository UUID, since this will be a different repository
than the old one -- this one will have a different revision 387 and
up than the old one did. This process will renumber the revisions
from 388 and up to be one less than they were before, so this will
mess up your log messages, if you ever recorded revision numbers into
your log messages. Also, this will mess up your externals if you have
revision numbers in your externals. Also, this will cause everyone to
have to check out new working copies.
You may find that dumping 388 thru HEAD doesn't work because some
revision in the range 388 to HEAD depended on the absent revision
387. If so, you'll have to skip that revision too.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-14 21:37:38 CET