Heres a note I found;
"Berkeley DB 4.1 happens to include a popular feature whereby frequent
updates -- even if serialized -- corrupt the database and lockup any
process reading or writing.
This feature has been dropped in 4.2. Alas, most current software (Sarge
and other distros like SuSE and RH) use 4.0 or 4.1."
I'd suggest a db upgrade.
On Thursday 24 June 2004 14:34, Stepan Kalichkin wrote:
> > I have testing out subversion 1.0.2 on a Fedora Red Hat
> > distribution. I am the only user of the subversion repository and
> > my usage is definitely light.
> >
> > Nevertheless, I am getting frequent DB corruption, approximately
> > once a day for the last week. Sometimes it happens when I try to
> > commit, sometimes it happens when I invoke WebSVN and it invokes a
> > svnlook command.
>
> I'am geting some problems on my SuSE 8.2 - corrupt every day.
> Is anybody can help?
>
>
> subversion-1.0.2-4
> subversion-doc-1.0.2-4
> db-4.0.14-249
>
> Tanks in advise
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 24 05:01:37 2004