|
From: Bart V. A. <bva...@ac...> - 2010-04-26 10:29:56
|
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. |
|
From: Ali K. <akh...@in...> - 2010-04-26 15:02:48
|
same here -------- Original Message -------- Subject: [Valgrind-developers] Valgrind repository problem From: Bart Van Assche <bva...@ac...> To: Valgrind Developers <val...@li...> Date: Mon Apr 26 2010 06:29:48 GMT-0400 (EDT) > 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 > |
|
From: Bjoern D. <bjo...@go...> - 2010-04-26 21:08:53
|
dito 2010/4/26 Ali Khalfan <akh...@in...>: > > same here > -------- Original Message -------- > Subject: [Valgrind-developers] Valgrind repository problem > From: Bart Van Assche <bva...@ac...> > To: Valgrind Developers <val...@li...> > Date: Mon Apr 26 2010 06:29:48 GMT-0400 (EDT) >> 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 > |
|
From: Julian S. <js...@ac...> - 2010-04-27 11:28:42
|
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 |
|
From: Julian S. <js...@ac...> - 2010-04-27 12:36:11
|
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 |
|
From: Rich C. <Ric...@me...> - 2010-04-27 13:14:27
|
Hi Julian, I stopped using the berkley db during svn trials using an early version of svn. I've sinced used fsfs type for all my svn repos and haven't had any issues. I think the bdb svn repo gets corrupted when an svn commit gets interrupted or canceled. It's a long known problem. Rich On Tue, 27 Apr 2010 13:44:32 +0200 Julian Seward <js...@ac...> 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 > -- |