On 11 Nov 2008, at 18:15, Jim Fulton wrote:
>
> The repository is back now. Much thanks to Christian Theune for
> providing a replication image.
>
> Jim
>
> --
> Jim Fulton
> Zope Corporation
>
And many thanks to you both for the work involved in setting up these
servers and keeping them runni
On Nov 11, 2008, at 8:52 AM, Jim Fulton wrote:
>
> I'm going to restore svn from a backup and see where that leaves
> us. I'm going to disable svn access while I work on this.
The repository is back now. Much thanks to Christian Theune for
providing a replication image.
Jim
--
Jim Fulto
On 11/11/08 4:10 PM, Izak Burger wrote:
Jim Fulton wrote:
I'm going to restore svn from a backup and see where that leaves us.
I'm going to disable svn access while I work on this.
Good luck :-) I know a little something about the hard work involved in
recovering subversion repos, in
Jim Fulton wrote:
> I'm going to restore svn from a backup and see where that leaves us.
> I'm going to disable svn access while I work on this.
Good luck :-) I know a little something about the hard work involved in
recovering subversion repos, in the last year we had TWO cases of
corrupted
I'm going to restore svn from a backup and see where that leaves us.
I'm going to disable svn access while I work on this.
Jim
--
Jim Fulton
Zope Corporation
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
On Tue, 2008-11-11 at 12:35 +0200, Marius Gedminas wrote:
> On Tue, Nov 11, 2008 at 08:51:28AM +0100, Adam GROSZER wrote:
> > Hello Stephan,
> >
> > svn: Can't open file '/svn/repos/main/db/revs/70320': No such file or
> > directory
> > program finished with exit code 1
> >
> > Seems that one re
On Tue, Nov 11, 2008 at 08:51:28AM +0100, Adam GROSZER wrote:
> Hello Stephan,
>
> svn: Can't open file '/svn/repos/main/db/revs/70320': No such file or
> directory
> program finished with exit code 1
>
> Seems that one revision did not get restored.
> It breaks also on "show log", where other f
Hi all,
We have a fairly large zope/plone site, with various bits of the site
split into separate databases, for example, all the members live in a
separate database. We also use persistent caches (which I think is
causing the problem).
We run zope 2.10.6, but we swapped out the ZODB with 3.8.
