Ahh... Thanks a bunch. The Python file indeed had similar errors. Now when I
run I get:
****************************************************
PatrickF_at_DESK28 /cygdrive/g/Subversion
$ ./verify-revisions.sh Repositories/eomis_1_6_12
/usr/bin/seq: invalid floating point argument: 93909
Try `/usr/bin/seq --help' for more information.
****************************************************
93909 is HEAD revision. Any ideas?
Patrick Fletcher
Marquis Software Development
Business Phone: (850) 877-8864 x132
Business Fax: (850) 877-0359
-----Original Message-----
From: Tony Sweeney [mailto:tsweeney_at_omnifone.com]
Sent: Tuesday, September 07, 2010 1:05 PM
To: Patrick Fletcher; Stefan Sperling
Cc: users_at_subversion.apache.org
Subject: RE: Subversion encountered a serious problem - during svn update
That file has DOS line endings in it. You can fix it using 'dos2unix
verify-revisions.sh'. The Python file may need the same treatment.
Tony.
-----Original Message-----
From: Patrick Fletcher [mailto:patrick.fletcher_at_marquisware.com]
Sent: 07 September 2010 18:00
To: 'Stefan Sperling'
Cc: users_at_subversion.apache.org
Subject: RE: Subversion encountered a serious problem - during svn
update
Thanks for super fast reply Stefan!!!! (yes, 4 exclamations)
> I've attached a helper script that you can use to run fsfsverify.py
across
multiple repositories.
I'm running windows here and I can't get this to work in Cygwin (please
excuse me if I'm just being ignorant - Unix/Python deficient)
************************************************************************
*
PatrickF_at_DESK28 ~/Desktop
$ ./verify-revisions.sh G:/Subversion/Repositories/eomis
./verify-revisions.sh: line 3: $'\r': command not found
./verify-revisions.sh: line 17: $'\r': command not found
./verify-revisions.sh: line 20: $'\r': command not found
./verify-revisions.sh: line 31: syntax error near unexpected token
`elif'
'/verify-revisions.sh: line 31: `elif which jot >/dev/null 2>/dev/null
************************************************************************
*
Googling around, I cannot find flag explanations for fsfsverify.py, and
only
really see examples about using -f flag to fix a single revision
identified
by the separate svnadmin verify (which as you know didn't report
anything
for my repo).
> Also, which version of Subversion are you running on the server?
Originally we had 1.6.3 as you saw, but in the time since the last
question
(not the one you replied to) I installed 1.6.12 on both client and
server.
Did a full dump (93309 revs), and loaded into a newly created repo. I
believe that I read this was the "recommended" way of "upgrading" and
figured it couldn't hurt anything in my situation so I did it even
though it
says no more format updates until a 2.... release.
> In general, please try to reproduce problems with the latest version
of
the software, always, on both clients and servers. We get quite a few
reports for old problems which have been fixed, but people missed the
fix
because they didn't upgrade.
Duly noted. I noticed my idiocy shortly after one of my other posts.
Thanks
again!!!!
Patrick Fletcher
Marquis Software Development
Business Phone: (850) 877-8864 x132
Business Fax: (850) 877-0359
-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Tuesday, September 07, 2010 11:50 AM
To: Patrick Fletcher
Cc: users_at_subversion.apache.org; 'Daniel Shahaf'; 'Andy Levy'
Subject: Re: Subversion encountered a serious problem - during svn
update
On Tue, Sep 07, 2010 at 11:19:21AM -0400, Patrick Fletcher wrote:
> I would really really appreciate anyone who has any information they
> can give me on this? I have not had any reply except for the "please
> don't attach images", which I replied to with full text explanation
> and apology for my ignorance (sry again!!)...
I think your problem sounds like corrupted revisions, but I'm not sure.
Please try to verify each revision of the repository with fsfsverify.py.
http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/fsf
sver
ify.py
fsfsverify.py can find corruptions that svnadmin verify doesn't report.
If fsfsverify.py finds a corrupt revision, you can try to fix the
revision
file with the -f option. But keep a backup of it before attempting to
fix.
I've attached a helper script that you can use to run fsfsverify.py
across
multiple repositories.
Also, which version of Subversion are you running on the server?
The pictures attached to your first post contain a screenshot of
Subversion
reporting itself as 1.6.3. Are you using that on your server?
If so, upgrade to 1.6.12 ASAP!!! (yes, 3 exclamation marks)
1.6.3 has a known security issue that led to error messages similar to
what
you are seeing, if my memory isn't playing tricks on me.
In general, please try to reproduce problems with the lastest version of
the
software, always, on both clients and servers. We get quite a few
reports
for old problems which have been fixed, but people missed the fix
because
they didn't upgrade.
Thanks,
Stefan
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Received on 2010-09-07 21:10:25 CEST