RE: svnadmin verify changing its diagnosis?

I'm afraid that this is not an answer to your question.

Are you using an filing system or a database backend? (I believe that this is indicated by the contents of the file db/fs-type in the repository.)

Also, did you see the problem more than once?

The reason for asking is that, if I understand correctly, the DB backend stores changes as reverse deltas backwards from the head revision, whereas the FS backend stores them as forwards deltas forwards from revision 0. So, only the database backend recalculates a chain of deltas during a commit.

I wonder if it's possible that the problem has disappeared due to a faulty delta being recalculated (following a commit).

Alternatively, I wonder whether it's possible to run svnadmin verify during a commit, and that what you saw was a repository database in a transient state.

Does anyone know?

Rob.

-----Original Message-----
From: Reedick, Andrew [mailto:Andrew.Reedick@BellSouth.com]
Sent: 05 October 2006 16:39
To: users@subversion.tigris.org
Subject: svnadmin verify changing its diagnosis?

I ran 'svn admin verify' yesterday on a repository and it failed
(returned non-zero and threw the 'malformed header' message.) Today
when I run 'svnadmin verify' it completes successfully for multiple
runs. fsfsverify.py (on a copy of the repos) didn't seem to find any
problems either. This using svn version 1.3.0 (r17949).

Anyone else ever see 'svnadmin verify' change its mind before?

Yesterday:
...
* Verified revision 797.
* Verified revision 798.
svnadmin: Found malformed header in revision file
<EOF>

Today:
...
* Verified revision 798.
* Verified revision 799.
* Verified revision 800.
* Verified revision 801.
* Verified revision 802.
* Verified revision 803.
...
* Verified revision 1306.
<EOF>

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

_____________________________________________________________________
This message has been checked for all known viruses by the MessageLabs Virus Scanning Service, on behalf of Celoxica Ltd.

This email and any files transmitted with it are confidential and
may be legally privileged. It is intended solely for the use of the
individual or entity to whom it is addressed. If you have received
this in error, please contact the sender and delete the material
immediately. Whilst this email has been swept for viruses, you
should carry out your own virus check before opening any
attachment. Celoxica Ltd accepts no liability for any loss or
damage which may be caused by software viruses or interception
or interruption of this email.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 11:38:52 2006