0

I have a slave replication of a VDFS master repository.

The problem is that slave repository file structure seems to be corrupted, but I could not manage to fix it. Currently it does not sync with the master repository.

Here is the error result after verification of the repository:

PS D:\Repositories>  svnadmin verify D:\Repositories\Repo1
* Verifying repository metadata ...
* Verifying metadata at revision 39 ...
* Verifying metadata at revision 62 ...
* Verifying metadata at revision 36 ...
* Verifying metadata at revision 63 ...
* Verifying metadata at revision 42 ...
* Verifying metadata at revision 37 ...
* Verifying metadata at revision 42 ...
* Verifying metadata at revision 61 ...
* Verifying metadata at revision 39 ...
* Verifying metadata at revision 36 ...
* Verifying metadata at revision 44 ...
* Verifying metadata at revision 62 ...
* Error verifying repository metadata.
svnadmin: E160004: Corrupt representation '57 2708143541 10935 57511 00000000000000000000000000000000 22c2da197fc962ba749df58940b6e9fce6e270c2 0-0/_0'
svnadmin: E160004: Malformed representation header

I guessed revision 62 to be corrupted so I tried to replace files from master repository to slave repository file structure.

I copied file named '62' from master to these paths respectively:

D:\Repositories\Repo1\db\data\revprops\0\62  -->copied from master to slave
D:\Repositories\Repo1\db\data\revs\0\62  -->copied from master to slave

But that did not fix the problem.

What should I do to fix this?

1 Answer 1

0

Please contact [email protected] if you need any assistance with the VisualSVN products.

  1. Do not replace revision files manually. It is generally considered good practice to treat the contents of D:\Repositories\Repo1\ as a black box that should not be modified by hand.

  2. Verify that the master VDFS repository is healthy. Use the Test-SvnRepository PowerShell cmdlet or run verification from the VisualSVN Server Manager console or as a background job.

  3. The datasets of the master and slave VDFS repositories are identical. In your scenario, if the slave is corrupted but the master is healthy, you can re-create the slave and it will fully replicate from the master. This should resolve the issue for you. But the first step in this recovery procedure is to confirm that the master repository is healthy.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.