> Regarding your specific repository:
> Somehow, log.3, log.4 and transactions had been severely corrupted with what
> appears to be random blocks of data from elsewhere on the disc. (other
> tables were also slightly affected)
>
> You were lucky, because only the transactions table was badly affected - if
> the transactions table is destroyed but the others are intact, the only loss
> of data are the revprops (i.e. log author and date).
> You were doubly lucky, in that although the transactions table was badly
> damaged, I was able to locate the uncorrupted data for each transaction skel
> (the format of data svn uses within bdb) by viewing the db file in a text
> editor, and doing copy/paste, thereby recovering all the data.
and a bloody marvel it is too. thanks max! re-loaded repos working like a charm, it doesn't even blush when i give it a hard look.
> Interesting side-note to any svn developers who know the bdb schema, who are
> reading this:
> Despite being mainly uncorrupted, all but one of the tables with a next-key
> row had that row reset to value "c".
hmmm... i was hoping that i might learn how to do this recovery thing but i think i'll just forget it.
> Anyway, so, repository fully recovered, and fsfs seems like quite a good
> idea for OS X users.
doesn't it just.
g
> Max.
>
>
> ---------------------------------------------------------------------
> 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 Fri Jul 16 23:02:46 2004