[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DB corruption of first day of subversion

From: Ritesh Nadhani <riteshp_at_webyog.com>
Date: 2004-11-11 11:56:58 CET

Hello,

----- Original Message -----
From: "Alex R. Mosteo" <alejandro@mosteo.com>
To: <users@subversion.tigris.org>
Sent: Thursday, November 11, 2004 3:12 PM
Subject: Re: DB corruption of first day of subversion

> Ritesh Nadhani wrote:
>> Hello again,
>>
>> ----- Original Message ----- From: "Jani Averbach" <jaa@jaa.iki.fi>
>> To: "Ritesh Nadhani" <riteshp@webyog.com>
>> Cc: <users@subversion.tigris.org>
>> Sent: Wednesday, November 10, 2004 11:25 PM
>> Subject: Re: DB corruption of first day of subversion
>>
 My advices from some months using Subversion, for when you arrive to try
it:
>
> - Avoid BerkeleyDB

Even I am use BerkelyDB. Do you say I should use FSFS?

> - Try some humongous imports/exports/commits/updates with lots of files.

The funny part is that it was doing ok with 2-3 commits for around 1 day.
After that I did one full checkout and one full commit from my home machine
to the server and then it started failing everytime. The checkout was of
around 10MB (it included doxygen documentation for the whole source code).
Do you think that might be the reason and I move to FSFS?

> - Make backups :)

For this to happen, my subversion has to work for atleast one week :)

>
>

Regards,
Ritesh

> ---------------------------------------------------------------------
> 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 Nov 11 11:57:21 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.