You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Thomas Martitz <ku...@rockbox.org> on 2014/08/13 22:04:39 UTC
svnrdump problem
Hello,
I have googled and found no trace of this issue. I must be the first one
hitting it.
The problem: I'm trying to save&restore a private SVN repository using
svnrdump. svnrdump load, though, errors out at revision 6 with "Too many
open files" error. I checked with strace and svnrdump is open()ing a
huge amount of files.
The command line is (note that the target repository is local) as per
svn book:
svnrdump dump svn://svnserver/path/to/repo | svnrdump load
file:///home/me/repo
file:///home/me/repo is a newly created repository (using svnadmin
create repo). The only enable and relax is to enable the pre-revprop-hook.
I tried to increase ulimit -n to 2048 without success. The issue also
appears if I use a temp file for the dump (svnrdump dump works fine,
apparently). Also dumping and loading each revision separately does not
help. It must be specific to the revision.
What could be the problem?
Best regards.
Re: svnrdump problem
Posted by jb...@icloud.com.
On Aug 13, 2014, at 1:04 PM, Thomas Martitz <ku...@rockbox.org> wrote:
> Hello,
>
> I have googled and found no trace of this issue. I must be the first one hitting it.
>
> The problem: I'm trying to save&restore a private SVN repository using svnrdump. svnrdump load, though, errors out at revision 6 with "Too many open files" error. I checked with strace and svnrdump is open()ing a huge amount of files.
>
> The command line is (note that the target repository is local) as per svn book:
> svnrdump dump svn://svnserver/path/to/repo | svnrdump load file:///home/me/repo
>
> file:///home/me/repo is a newly created repository (using svnadmin create repo). The only enable and relax is to enable the pre-revprop-hook.
>
> I tried to increase ulimit -n to 2048 without success. The issue also appears if I use a temp file for the dump (svnrdump dump works fine, apparently). Also dumping and loading each revision separately does not help. It must be specific to the revision.
>
> What could be the problem?
>
> Best regards.
What version of svn? What OS? You know the drill.
RE: svnrdump problem
Posted by Grant Schoep <gs...@digitalglobe.com>.
>> 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, it lists the open file handles. It's a bit easier to figure out what files its opening than strace.
This electronic communication and any attachments may contain confidential and proprietary
information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee
responsible for delivering this communication to the intended recipient, or if you have received
this communication in error, please do not print, copy, retransmit, disseminate or
otherwise use the information. Please indicate to the sender that you have received this
communication in error, and delete the copy you received. DigitalGlobe reserves the
right to monitor any electronic communication sent or received by its employees, agents
or representatives.
Re: svnrdump problem
Posted by Philip Martin <ph...@wandisco.com>.
Thomas Martitz <ku...@rockbox.org> writes:
> 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?
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Re: svnrdump problem
Posted by Thomas Martitz <ku...@rockbox.org>.
Am 13.08.2014 22:13, schrieb Andreas Stieger:
> Hi,
>
> On 13/08/14 21:04, Thomas Martitz wrote:
>> svnrdump load, though, errors out at revision 6 with "Too many open
>> files" error. I checked with strace and svnrdump is open()ing a huge
>> amount of files.
>>
>> The command line is (note that the target repository is local) as per
>> svn book:
>> svnrdump dump svn://svnserver/path/to/repo | svnrdump load
>> file:///home/me/repo
>
> Is there any reason why you don't use svnadmin load for the second part?
>
> Andreas
>
I wasn't aware that svnadmin can load svnrdump created dumps (perhaps a
hint in the svnrdump section of the would be helpful). Thanks you for
this advice.
I will try it with svnadmin load. But I don't know yet whether we'll
need to target to a real remote machine in the actual use case. I used
the local repository in my example above because I'm playing locally
with svnrdump.
Shouldn't the svnrdump issue be investigated regardless?
Best regards.
Re: svnrdump problem
Posted by Andreas Stieger <an...@gmx.de>.
Hi,
On 13/08/14 21:04, Thomas Martitz wrote:
> svnrdump load, though, errors out at revision 6 with "Too many open
> files" error. I checked with strace and svnrdump is open()ing a huge
> amount of files.
>
> The command line is (note that the target repository is local) as per
> svn book:
> svnrdump dump svn://svnserver/path/to/repo | svnrdump load
> file:///home/me/repo
Is there any reason why you don't use svnadmin load for the second part?
Andreas