> -----Original Message-----
> From: John Szakmeister [mailto:email@example.com]
> Sent: Thursday, May 27, 2004 3:55 AM
> To: Garrett Rooney
> Cc: Natalya Pyalling; firstname.lastname@example.org
> Subject: Re: Suddenly corrupted Subversion repository.
> On Wednesday 26 May 2004 19:32, Garrett Rooney wrote:
> > John Szakmeister wrote:
> > > On Wednesday 26 May 2004 05:19, Natalya Pyalling wrote:
> > >>Additional info:
> > >>After issueing 'svnadmin verify' I have in /var/log/messages
> > >>
> > >>May 26 13:11:47 vcs kernel: Out of Memory: Killed process 11822
> > >>(svnadmin).
> > >>May 26 13:11:55 vcs kernel: Out of Memory: Killed process 11558
> > >>May 26 13:12:06 vcs su(pam_unix): session closed for user
> > >
> > > Oof, that can't be good. Here's what's probably happening.
> > > recover' grabs an exclusive lock on the repository (I can't
> > > hand if 'svnadmin verify' does the same). If svnadmin is dying
> > > this, the exclusive lock is never freed, and the apache ends up
> > > for the repository to become free. It, of course, never does.
> > > the reason you keep timing out.
> > Umm, I believe that lock should actually be released when the
> > exits, we use apr_file_lock to manage the lock, and that just calls
> > flock under the hood, IIRC flock's locks only last until the process
> It looks like your right... although, APR can use either fcntl() or
> depending on the system. Either way, the lock should be released.
> Natalya, can you at least take a look at the memory consumption?
This is memory on our server.
[root@vcs root]# free -m
total used free shared buffers
Mem: 1008 992 15 0 128
-/+ buffers/cache: 305 702
Swap: 1027 0 1027
During the problem, I was monitoring the server. So all memory and
100%CPU were used by apache or svnadmin.
May be the problem is located in the size of our repository?
[root@vcs root]# du -sh /var/Repository/repos
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu May 27 11:22:51 2004