Alexandre Reis wrote:
> Guys,
>
> I'm new to the list, so I'd first like to introduce myself and tell a bit
> of
> my story with Subversion...
>
> I'm a developer for Datasul Paranaense, a corporate software developer's
> local franchise. We develop custom solutions for Datasul ERP products.
>
> Our use of subversion consists on having every customer's projects on it,
> allowing us to have effective group development, and also for security
> sake.
>
> We've been using Subversion sice around August with no problems, including
> a
> version upgrade (and a BDB version upgrade), which forced us to dump/load
> the BDB database.
>
> After the dump/load, Subversion has corrupted quite frequently, but until
> now, we could recover it with svnadmin recover.
>
> This time it really crashed, so I tried recovering it with
> db_recover -cve,
> and it did recover itself fine.
>
> So I ran svnadmin verify on the repository, and it ran fine, until
> reaching
> revision 629 (We're currently on revision 1925). It simply aborts after
> getting to that revision.
Is there any more detail you can give, further than "simply aborts"?
> Same thing goes for svnadmin dump.
>
> I'd like to somehow dump this database and load it into a new database, to
> get rid of this corrupt revision.
>
> I hope someone can help me out with this, as I've searched everywhere and
> there doesn't seem to be a way to skip this revision while dumping, or
> something that can fix it.
Can you make the broken repository available to me (privately)? I will
inspect it and recover what I can.
Normally I would attempt to troubleshoot by email first, but a simple abort
doesn't really give me much to go on.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 20 16:13:01 2005