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/fsfsverify.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