Re: [Valgrind-developers] Valgrind repository problem

[Julian S. <js...@ac...>]

The svn server is running again now, but I will have to mess the
vex repo more later today.

J

On Tuesday 27 April 2010, Julian Seward wrote:
> Yes, something is not good w/ the repo.  For some reason the svn
> server created about 5GB of Berkeley DB log files and ran out of
> space.  Now the vex repo is corrupted, or at least, "svnadmin
> hotcopy" is not happy, and no amount of "svnadmin recover" fixes it,
> even though "svnadmin verify" says it's fine.
>
> So I am inclined to go back to the last vex repo backup and reland
> r1968 through r1976.  The other repos (valgrind, valgrind-www) appear
> to be OK.
>
> J
>
> On Monday 26 April 2010, Bart Van Assche wrote:
> > Hello,
> >
> > Is there something wrong with the Valgrind repository ? I get the
> > following error message since about three days when I try to access
> > the Valgrind repository:
> >
> > $ svn ls svn://svn.valgrind.org/valgrind
> > svn: Berkeley DB error for filesystem '/home/svn/repos/valgrind/db'
> > while opening 'nodes' table:
> > Cannot allocate memory
> > svn: bdb: Lock table is out of available locker entries
> >
> > Bart.
> >
> > -------------------------------------------------------------------------
> >-- --- _______________________________________________
> > Valgrind-developers mailing list
> > Val...@li...
> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
> ---------------------------------------------------------------------------
>--- _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers