You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jules Herr <jh...@inmedius.com> on 2011/03/14 15:42:16 UTC
Failed SVN Verify Logs
Hi,
I had a failed SVN VERIFY and am submitting the log files as directed by the
application. Any and all help is greatly appreciated!
Thanks
Jules
Here is the screen shot and log files of the svnadmin verify which I did in
Windows against the kxsrc Subversion repository
--
Jules Herr
Technology Solutions Provider
jherr@inmedius.com
skpe: jules.herr
Re: Failed SVN Verify Logs
Posted by Jules Herr <jh...@inmedius.com>.
Hi Michael, Ankush and everyone else involved, thanks for you help and
suggestions to date. I will continue attempting to solve this issue
until we reach a resolution.
Attempted to run fsfsverify.py on my hotcopied version of the
repository. No success. Output is included below:
C:\fsfsverify\fsfsverify>fsfsverify.py -f Z:/hotcopy_314/db/revs/607
NodeRev Id: 0.0.r607/16044
type: dir
pred: 0.0.r606/7312599
text: PLAIN 607 15924 107 107 2cfb1cc2b14944cc284371f567e7b3d7
cpath: /
copyroot: 0 /
dir contents:
kits: [dir, 7f.0.r553/463]
code: [dir, 2.6.r607/15771]
internal: [dir, 2tj.0.r582/6535]
NodeRev Id: 2.6.r607/15771
type: dir
pred: 2.6.r606/7312320
text: PLAIN 607 15274 484 484 af645977d85c473effc75e62415404cc
cpath: /code
copyroot: 24 /code
dir contents:
vitalsigns: [dir, 1cg.6.r161/5569]
omnibus: [dir, 3.8.r524/547]
PWC_TESTs: [dir, 15r1.6.r406/225055]
IFS_CD: [dir, 9on.6.r429/352]
custom: [dir, 1pj.6.r604/173783]
omnibus6: [dir, 170o.6.r607/15109]
IBM_Tests: [dir, 15rg.6.r502/189119]
CorporateWeb: [dir, 3kp.6.r297/16099]
omnibusLicense: [dir, 3at.6.r234/5577]
omnibusClient: [dir, 36p.6.r206/128653]
ISG: [dir, 15v8.6.r573/50408]
ISG30: [dir, 2u9.6.r605/5046929]
NodeRev Id: 170o.6.r607/15109
type: dir
pred: 170o.6.r606/7311655
text: PLAIN 607 15023 73 73 df8dc903c331da7f17bd89e00ab21185
cpath: /code/omnibus6
copyroot: 24 /code
dir contents:
trunk: [dir, 170p.6.r607/14850]
tags: [dir, 170q.6.r540/0]
NodeRev Id: 170p.6.r607/14850
type: dir
pred: 170p.6.r606/7311394
text: PLAIN 607 14649 188 188 b292ec37f07809f3fc66c862cd21a3bc
cpath: /code/omnibus6/trunk
copyroot: 24 /code
dir contents:
docs: [dir, 170r.6.r584/3288457]
src: [dir, 18x7.6.r607/14475]
build: [dir, 18x5.6.r607/8223]
lib: [dir, 18x6.6.r606/7305608]
proto: [dir, 18vh.6.r574/436101]
NodeRev Id: 18x7.6.r607/14475
type: dir
pred: 18x7.6.r606/7311013
text: PLAIN 607 14422 40 40 13883f96e91486214b854ab68fbcc75e
cpath: /code/omnibus6/trunk/src
copyroot: 24 /code
dir contents:
java: [dir, 18x8.6.r607/14243]
NodeRev Id: 18x8.6.r607/14243
type: dir
pred: 18x8.6.r606/7310778
text: PLAIN 607 14191 39 39 19c447f0e8f1f62b71d0d08256f47ec4
cpath: /code/omnibus6/trunk/src/java
copyroot: 24 /code
dir contents:
com: [dir, 18x9.6.r607/14008]
NodeRev Id: 18x9.6.r607/14008
type: dir
pred: 18x9.6.r606/7310540
text: PLAIN 607 13957 38 38 9ba5ae313eb96f2ab3c7a3303842597b
cpath: /code/omnibus6/trunk/src/java/com
copyroot: 24 /code
dir contents:
kx: [dir, 18xa.6.r607/13771]
NodeRev Id: 18xa.6.r607/13771
type: dir
pred: 18xa.6.r606/7310300
text: PLAIN 607 13715 43 43 cb878d2ac9f070ac2bf9ef20becf9c0f
cpath: /code/omnibus6/trunk/src/java/com/kx
copyroot: 24 /code
dir contents:
omnibus: [dir, 18xb.6.r607/13519]
NodeRev Id: 18xb.6.r607/13519
type: dir
pred: 18xb.6.r606/7310045
text: PLAIN 607 13355 151 151 23b0fc71e626efa615cd4e322af78693
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus
copyroot: 24 /code
dir contents:
lmssvc: [dir, 18xg.6.r607/12655]
test: [dir, 18xh.6.r607/8677]
domain: [dir, 18xc.6.r607/11493]
util: [dir, 18xi.6.r607/13156]
NodeRev Id: 18xg.6.r607/12655
type: dir
pred: 18xg.6.r606/7309403
text: PLAIN 607 12491 151 151 c48b9cd7aef9cfd18f0dd38ee11e8f4f
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc
copyroot: 24 /code
dir contents:
LoginResult.java: [file, 18xo.31!.r607/12197]
Auditor.java: [file, 18xn.6.r607/11981]
LoginSvc.java: [file, 18y0.31".r607/11696]
NodeRev Id: 18xo.31!.r607/12197
type: file
pred: 18xo.31∟.r606/7308929
text: UNKNOWN 584 2404 840 1982 1701913b5499bee7137e4d59b39de6f2
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc/LoginResult.java
copyfrom: 606 /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc/LoginResult.j
ava-KEEP
Skipping text rep since it isn't present in the current rev
NodeRev Id: 18xn.6.r607/11981
type: file
pred: 18xn.6.r584/3285690
text: DELTA 607 2223 55 1046 da04f16447a1d0819af36c53974040e6
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc/Auditor.java
copyroot: 24 /code
<Svndiff so: 2242 ver: 1>
NodeRev Id: 18y0.31".r607/11696
type: file
pred: 18y0.31↔.r606/7308645
text: DELTA 607 0 333 4113 ba96b8ca73ded9af13ae14ffa6f22015
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc/LoginSvc.java
copyfrom: 606 /code/omnibus6/trunk/src/java/com/kx/omnibus/lmssvc/LoginSvc.java
-KEEP
<Svndiff so: 23 ver: 1>
NodeRev Id: 18xh.6.r607/8677
type: dir
pred: 18xh.6.r606/7306066
text: PLAIN 607 8614 50 50 ac87d243a772a0bafd4bd56d3ec19cea
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/test
copyroot: 24 /code
dir contents:
UserTest.java: [file, 18y2.6.r607/8399]
NodeRev Id: 18y2.6.r607/8399
type: file
pred: 18y2.6.r606/7305784
text: DELTA 607 815 1001 6522 20d9283d756f0ac65e7295a7216c5d63
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/test/UserTest.java
copyroot: 24 /code
<Svndiff so: 835 ver: 1>
NodeRev Id: 18xc.6.r607/11493
type: dir
pred: 18xc.6.r606/7308441
text: PLAIN 607 11364 116 116 9ffbd19c119bc83d6ac1c458be715160
cpath: /code/omnibus6/trunk/src/java/com/kx/omnibus/domain
copyroot: 24 /code
dir contents:
app: [dir, 18xd.6.r607/9914]
property: [dir, 18xe.6.r584/3282810]
user: [dir, 18xf.6.r607/11156]
Traceback (most recent call last):
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 1120, in <module>
for noderev in strategy:
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 839, in _nodeWalker
for x in self._nodeWalker():
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 832, in _nodeWalker
noderev = NodeRev(self.f, self.currentRev)
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 723, in __init__
self.dir = getDirHash(f)
File "C:\fsfsverify\fsfsverify\fsfsverify.py", line 509, in getDirHash
(type, txn) = value.split(' ')
ValueError: too many values to unpack
Thanks
jules
On Wed, Mar 16, 2011 at 7:39 AM, Michael Diers <md...@elego.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2011-03-16 00:38, Jules Herr wrote:
> [...]
>> hotcopy completed, failure with snvadmin verify on revision 607 in both
>> the old repository and and the newly created hotcopied repository.
> [...]
>
> Jules,
>
> you should probably try fsfsverify. Be sure to run it on a copy of your
> repository. You may have to run the repair step repeatedly before it
> converges.
>
> http://www.szakmeister.net/fsfsverify/
>
> http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/fsfsverify.py
>
> - --
> Michael Diers, elego Software Solutions GmbH, http://www.elego.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2AoYkACgkQcEKlWnqVgz3oiQCfW9kycVoyNVtNm7XLl+4EUi+E
> aZQAoInT4Cwb+CCBQTfZNL1ErIcZO4VT
> =sOGc
> -----END PGP SIGNATURE-----
>
--
Jules Herr
Technology Solutions Provider
jherr@inmedius.com
skpe: jules.herr
Re: Failed SVN Verify Logs
Posted by Michael Diers <md...@elego.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2011-03-16 00:38, Jules Herr wrote:
[...]
> hotcopy completed, failure with snvadmin verify on revision 607 in both
> the old repository and and the newly created hotcopied repository.
[...]
Jules,
you should probably try fsfsverify. Be sure to run it on a copy of your
repository. You may have to run the repair step repeatedly before it
converges.
http://www.szakmeister.net/fsfsverify/
http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/fsfsverify.py
- --
Michael Diers, elego Software Solutions GmbH, http://www.elego.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2AoYkACgkQcEKlWnqVgz3oiQCfW9kycVoyNVtNm7XLl+4EUi+E
aZQAoInT4Cwb+CCBQTfZNL1ErIcZO4VT
=sOGc
-----END PGP SIGNATURE-----
Re: Failed SVN Verify Logs
Posted by Jules Herr <jh...@inmedius.com>.
On Tue, Mar 15, 2011 at 10:44 AM, ankush chadha
<an...@yahoo.com>wrote:
> Try running following commands to grab info about r607 on the server side
>
> svn info file:///<Path_To_Repository> -r 607
>
> svn log file:///<Path_To_Repository> -r 607
>
>
C:\Documents and Settings\julesh>svn info
https://svn.knowledgextensions.com/svn
-r 607
Path: svn
URL: https://svn.knowledgextensions.com/svn
Repository Root: https://svn.knowledgextensions.com/svn
Repository UUID: cd97b3e7-f46f-2e48-baaf-a76abbe1cd95
Revision: 607
Node Kind: directory
Last Changed Author: andyg
Last Changed Rev: 607
Last Changed Date: 2007-11-01 17:38:57 -0400 (Thu, 01 Nov 2007)
C:\Documents and Settings\julesh>svn log
https://svn.knowledgextensions.com/svn
-r 607
------------------------------------------------------------------------
r607 | andyg | 2007-11-01 17:38:57 -0400 (Thu, 01 Nov 2007) | 1 line
------------------------------------------------------------------------
C:\Documents and Settings\julesh>
>
> Also check if 607 file is located under following folders
> <Path_To_Repository>\db\revs
> <Path_To_Repository>\db\revprops
>
>
Both exist
> hotcopy is another option to restore the svn repository. I have used
> svnadmin dump before but never faced this problem. Make sure that you are
> using same version of binaries throughout.
>
>
hotcopy completed, failure with snvadmin verify on revision 607 in both the
old repository and and the newly created hotcopied repository.
I'm at a loss. What can I do next?
> You should also mirror your svn repository to reduce downtime and
> surprises.
>
>
>
Thats all well and good unless your mirror is corrupted too.
Thanks
jules
------------------------------
> *From:* Jules Herr <jh...@inmedius.com>
> *To:* ankush chadha <an...@yahoo.com>
> *Cc:* users@subversion.apache.org
> *Sent:* Mon, March 14, 2011 1:48:25 PM
> *Subject:* Re: Failed SVN Verify Logs
>
> Yes we're using the binaries for Collabnet, not exactly sure which version
> it is - is there an easy way to determine?
>
> Not sure if I can access revision 607, is there a way to determine what
> files are in a particular revision?
>
> It appears I can run verification on all revisions 1-606 and I'm running a
> verify on 608-8968 right now, seems to be running OK.
>
> Users have had no problems accessing the repository, and this problem has
> only made itself evident since we've tried to move our SVN repo via dump
> files to a new server.
>
> I'm currently attempting a hot-copy as this has apparently fixed another
> users repo who was experiencing similar symptoms:
>
>
> http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup
>
>
> <http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup>
> Thanks
> jules
>
>
>
>
> On Mon, Mar 14, 2011 at 1:39 PM, ankush chadha <ankushchadha2003@yahoo.com
> > wrote:
>
>> Which subversion binaries are you using? Are these the ones from
>> Collabnet?
>>
>> Can you access revision 607? Can you also try resuming the verification
>> process from revision 607?
>>
>> Ankush
>>
>>
>> ------------------------------
>> *From:* Jules Herr <jh...@inmedius.com>
>> *To:* users@subversion.apache.org
>> *Sent:* Mon, March 14, 2011 10:42:16 AM
>> *Subject:* Failed SVN Verify Logs
>>
>> Hi,
>>
>> I had a failed SVN VERIFY and am submitting the log files as directed by
>> the application. Any and all help is greatly appreciated!
>>
>> Thanks
>> Jules
>>
>>
>>
>> Here is the screen shot and log files of the svnadmin verify which I did
>> in Windows against the kxsrc Subversion repository
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> Jules Herr
>> Technology Solutions Provider
>> jherr@inmedius.com
>> skpe: jules.herr
>>
>>
>>
>>
>
>
> --
>
> Jules Herr
> Technology Solutions Provider
> jherr@inmedius.com
> skpe: jules.herr
>
>
>
>
Re: Failed SVN Verify Logs
Posted by ankush chadha <an...@yahoo.com>.
Try running following commands to grab info about r607 on the server side
svn info file:///<Path_To_Repository> -r 607
svn log file:///<Path_To_Repository> -r 607
Also check if 607 file is located under following folders
<Path_To_Repository>\db\revs
<Path_To_Repository>\db\revprops
hotcopy is another option to restore the svn repository. I have used svnadmin
dump before but never faced this problem. Make sure that you are using same
version of binaries throughout.
You should also mirror your svn repository to reduce downtime and surprises.
Ankush
________________________________
From: Jules Herr <jh...@inmedius.com>
To: ankush chadha <an...@yahoo.com>
Cc: users@subversion.apache.org
Sent: Mon, March 14, 2011 1:48:25 PM
Subject: Re: Failed SVN Verify Logs
Yes we're using the binaries for Collabnet, not exactly sure which version it is
- is there an easy way to determine?
Not sure if I can access revision 607, is there a way to determine what files
are in a particular revision?
It appears I can run verification on all revisions 1-606 and I'm running a
verify on 608-8968 right now, seems to be running OK.
Users have had no problems accessing the repository, and this problem has only
made itself evident since we've tried to move our SVN repo via dump files to a
new server.
I'm currently attempting a hot-copy as this has apparently fixed another users
repo who was experiencing similar symptoms:
http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup
Thanks
jules
On Mon, Mar 14, 2011 at 1:39 PM, ankush chadha <an...@yahoo.com>
wrote:
Which subversion binaries are you using? Are these the ones from Collabnet?
>
>Can you access revision 607? Can you also try resuming the verification process
>from revision 607?
>
>Ankush
>
>
>
>
>
>
________________________________
From: Jules Herr <jh...@inmedius.com>
>To: users@subversion.apache.org
>Sent: Mon, March 14, 2011 10:42:16 AM
>Subject: Failed SVN Verify Logs
>
>
>Hi,
>
>
>I had a failed SVN VERIFY and am submitting the log files as directed by the
>application. Any and all help is greatly appreciated!
>
>
>Thanks
>Jules
>
>
>
>
>
>
>Here is the screen shot and log files of the svnadmin verify which I did in
>Windows against the kxsrc Subversion repository
>
>
>
>
>
>--
>
>Jules Herr
>Technology Solutions Provider
>jherr@inmedius.com
>skpe: jules.herr
>
>
>
>
--
Jules Herr
Technology Solutions Provider
jherr@inmedius.com
skpe: jules.herr
Re: Failed SVN Verify Logs
Posted by Jules Herr <jh...@inmedius.com>.
Yes we're using the binaries for Collabnet, not exactly sure which version
it is - is there an easy way to determine?
Not sure if I can access revision 607, is there a way to determine what
files are in a particular revision?
It appears I can run verification on all revisions 1-606 and I'm running a
verify on 608-8968 right now, seems to be running OK.
Users have had no problems accessing the repository, and this problem has
only made itself evident since we've tried to move our SVN repo via dump
files to a new server.
I'm currently attempting a hot-copy as this has apparently fixed another
users repo who was experiencing similar symptoms:
http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup
<http://jim.bernatowicz.net/fix-corrupt-svn-repository-fails-svn-verify-hotcopy-backup>
Thanks
jules
On Mon, Mar 14, 2011 at 1:39 PM, ankush chadha
<an...@yahoo.com>wrote:
> Which subversion binaries are you using? Are these the ones from Collabnet?
>
> Can you access revision 607? Can you also try resuming the verification
> process from revision 607?
>
> Ankush
>
>
> ------------------------------
> *From:* Jules Herr <jh...@inmedius.com>
> *To:* users@subversion.apache.org
> *Sent:* Mon, March 14, 2011 10:42:16 AM
> *Subject:* Failed SVN Verify Logs
>
> Hi,
>
> I had a failed SVN VERIFY and am submitting the log files as directed by
> the application. Any and all help is greatly appreciated!
>
> Thanks
> Jules
>
>
>
> Here is the screen shot and log files of the svnadmin verify which I did in
> Windows against the kxsrc Subversion repository
>
>
>
>
>
>
>
>
> --
>
> Jules Herr
> Technology Solutions Provider
> jherr@inmedius.com
> skpe: jules.herr
>
>
>
>
--
Jules Herr
Technology Solutions Provider
jherr@inmedius.com
skpe: jules.herr