[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Trunk bug, serf, sqlite, or just me?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Fri, 4 May 2012 17:16:16 -0400

On 05/04/2012 04:37 PM, Mark Phippard wrote:
> $ svn up --set-depth=infinity ev2-export/
> Updating 'ev2-export':


> subversion/libsvn_subr/sqlite.c:585: (apr_err=200030)
> svn: E200030: sqlite: unable to open database file
> This could be due to my SQLite version? I was getting similar errors
> with my own repository but after it installed a few of the files.

I can't explain this one.

> $ svn up --set-depth=infinity .
> Updating '.':
> ... (just a few files snipped)
> A notes/obliterate/presentations/why.odp
> subversion/svn/update-cmd.c:163: (apr_err=24)
> subversion/libsvn_client/update.c:611: (apr_err=24)
> subversion/libsvn_client/update.c:552: (apr_err=24)
> subversion/libsvn_client/update.c:413: (apr_err=24)
> subversion/libsvn_wc/adm_crawler.c:858: (apr_err=24)
> subversion/libsvn_ra_serf/update.c:2639: (apr_err=24)
> subversion/libsvn_ra_serf/util.c:1837: (apr_err=24)
> subversion/libsvn_ra_serf/util.c:1818: (apr_err=24)
> subversion/libsvn_ra_serf/update.c:1281: (apr_err=24)
> subversion/libsvn_wc/update_editor.c:3688: (apr_err=24)
> subversion/libsvn_wc/adm_files.c:342: (apr_err=24)
> subversion/libsvn_subr/stream.c:888: (apr_err=24)
> subversion/libsvn_subr/io.c:4320: (apr_err=24)
> subversion/libsvn_subr/io.c:4135: (apr_err=24)
> svn: E000024: Can't create temporary file from template
> '/Users/markphip/work/trunk-testing/subversion/.svn/tmp/svn-XXXXXX':
> Too many open files
> So this gets further before getting a different error.

I *might* be able to explain at least a portion of this one.

My code calls the (new) get_wc_contents RA callback to get a read stream for
the pristine text matching the specified SHA1. This will open the pristine
file. The file remains open until its contents are consumed (whenever
Serf/ra_serf get around to doing so per the pipelined approach taken to
GET/HEAD/PROPFINDs during updates). I suppose if the code which is cramming
pipelined requests (the result of parsing the initial REPORT) into the queue
outpaces the code that's handling those requests, you could wind up with too
many open files.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2012-05-04 23:16:51 CEST

This is an archived mail posted to the Subversion Dev mailing list.