> From: Gerald Richter [mailto:richter@ecos.de]
> Sent: 06 June 2002 07:28
> > You can work around the problem by checking-out revision zero and
> > then updating the working copy
> >
> > % svn co -r 0 -d wc http://host/repo
> > % svn up wc
> >
> > These commands use much less memory in the server process (about
> > twenty megabytes instead of two or three hundred in my tests.)
> >
>
> That makes things better, now httpd grows to 130MB during the update, but I
> still get only 2/3 of the files out of the repository then the server closes
> the connection (without any error message in syslog or error_log).
>
> BTW. I my repository only contains 4200 files and not 42,000 as I originaly
> wrote. Must have been too tired when I read this extra zero... (but really
> 45MByte)
>
> After this update the DB Files are soemhow locked and the only thing that
> had help is to run a db_recover on the db files, otherwise any access to the
> repository simply hangs.
>
> When I now try to run a svn up in the half checked out working copy, I get
> errors about file not found in transaction. Seems there is still something
> left from the failed update, also I have rebooted the machine in between.
>
> I try to investigate further. Any ideas are welcome.
Can you try doubling the max locks/etc in repos/db/DB_CONFIG? I'm wondering
if that will have any impact.
> Gerald
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 6 07:31:36 2002