>> Shouldn't the svnrdump issue be investigated regardless?
>It would help if you provided more information: which version of Subversion
>are you using? What sort of changes does the problem revision contain? Which
>>files are not being closed?
Run "lsof" on the process when it is running
SVN Version: 1.8.8 (part of a Collabnet 4.0.5 install)
OS: RHEL 5.10
So today I just got an alert that my disk space for dumps ran out. The
dumps typically take about 2.4 gigs of space uncompressed. I noticed
yesterdays suddenly went to 4 gigs.
And now, it hits about 40 gigs before I run out
I'm running
SVN client (svn, version 1.8.8 (r1568071, from Collabnet RPM) (NOTE I've
tried a few different SVN versions on different machines for client side,
same results)
SVN server is running Subversion Edge 4.0.5
So I was trying to get an external tool(Crucible) to interact with our SVN
databa
