Brad <svn@molandernet.com> writes:
> I have 18 fsfs repositories that I recently upgraded to 1.2.1 from 1.1.
> I dumped and reloaded them as recommended and everything has been fine
> for a week. One repository however now repeatedly gets "svnadmin: Found
> malformed header in revision file" when people try to checkin or browse
> it via websvn. This is a decent sized project at 1.5GB and 4k files.
>
> svnadmin recover seems to do nothing and return success every time. I
> created a duplicated repository and removed the most recent transaction
> from revs and decremented the revision number in db/current. The
> repository seems to function now, however I am curious as to the effects
> this will have on WCs, especially for the user that created this
> document (binary file).
>
> Have I followed the correct and best procedure for this recovery? Have I
> inadvertently caused more harm than good by doing this? Anything else I
> could do to either get the corrupted revision back?
That was a clever solution. Just let the working copy users know that
they should re-check-out.
Can you post the corrupt rev file?
-Karl
--
www.collab.net <> CollabNet | Distributed Development On Demand
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 25 23:54:11 2005