Hi
Ahh, Following the other thread on this mailing list regarding repository
corruption ("Repository keeps corrupting") it just hit me..
After I upgraded to 0.28.2, I forgott to set the sticky-group bit on my svn
directoryes. Might permission issues be the source of my problem ?
Best regards,
Vidar
On Thursday 04 September 2003 18:40, Vidar wrote:
> Ups, forgot to reply to the list as well:
>
> ---------- Forwarded Message ----------
>
> Subject: Re: svn server crashes, corrupt repository
> Date: Thursday 04 September 2003 16:34
> From: Vidar <vl-list@ez.no>
> To: Ben Collins-Sussman <sussman@collab.net>
>
> Hi
>
> Thank you for your fast reply
>
> > This error means you've run out of lockfiles, I think. (Is that
> > correct, Sander?) That's strange, because this error is exactly the
> > bug that 0.28.2 is supposed to fix (compared to 0.28.0 and 0.28.1.)
> > Are you *sure* that your mod_dav_svn module is 0.28.2?
>
> I uses the rpms which is (was ??? seems to be offline now) available here
> http://summersoft.fay.ar.us/pub/subversion/i386/subversion-latest/redhat-7.
>x/
>
> and rpm reveals:
> # rpm -qf /usr/local/apache2/modules/mod_dav_svn.so
> subversion-server-0.28.2-6947
>
> So yes, I am pretty sure I use 0.28.2
>
> Best regards,
> Vidar
>
> On Thursday 04 September 2003 16:06, you wrote:
> > Vidar <vl-list@ez.no> writes:
> > > However, We have now been running 0.28.2 for 1 day and now it has
> > > crashed again.
> > >
> > > I get:
> > > $ svnlook youngest nextgen
> > > svn: Berkeley DB error
> > > svn: Berkeley DB error while checkpointing after Berkeley DB
> > > transaction for filesystem nextgen/db:
> > > DB_INCOMPLETE: Cache flush was unable to complete
> > >
> > > Do I have to run "svnadmin recover" ?
> >
> > This error means you've run out of lockfiles, I think. (Is that
> > correct, Sander?) That's strange, because this error is exactly the
> > bug that 0.28.2 is supposed to fix (compared to 0.28.0 and 0.28.1.)
> > Are you *sure* that your mod_dav_svn module is 0.28.2?
> >
> > I think you need to run recovery, yes.
> >
> > > Ealier when we got stall lock (in older versions) on the repository, I
> > > have just done a "shortcut" and delete the __db.00* files. Is this safe
> > > ?
> >
> > Unless you understand BerkeleyDB *very* well, this sounds like risky
> > behavior to me. I wouldn't do that.
>
> --
> vidar
>
> -------------------------------------------------------
--
vidar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 4 20:03:25 2003