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

RE: Unable to dump repository

From: Tony Thompson <Tony.Thompson_at_stone-ware.com>
Date: 2007-03-15 20:57:49 CET

Actually, it seems I have several repositories that are in this same
state. Not sure if the update to 1.4.3 had something to do with it or
not. One of the repositories that is corrupt is a new empty repository
and I can make that available (not sure if I can send attachments but I
attached it anyway). If there is a way to fix this, I have some others
that need fixed but I will have to fix them myself (with good
instructions of course :) ).
 
Tony

________________________________

From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Thursday, March 15, 2007 3:22 PM
To: Tony Thompson
Cc: users@subversion.tigris.org
Subject: Re: Unable to dump repository

On 3/15/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:

        On 3/15/07, Tony Thompson < Tony.Thompson@stone-ware.com
<mailto:Tony.Thompson@stone-ware.com> > wrote:
        

                It does tell me what the last revision number was that
it dumped but, there is lots of stuff in the repository after that
revision that I don't want to lose.

        

        I have never had to recover a problem like this. If you can
dump up to the problem, then skip that revision and dump what comes
after, you might be able to fix the problem. Just load the first dump
file. Do some random commit to use up the next revision number, and
then load the second dump file. The random commit is not strictly
necessary if you do not care about the revision numbers changing.
        
        Mark
        
         
        It appears that there are other revisions after my corrupt
revision that also have that same issue. It would be nice if there was
a repair option that could just fix it for me :) ... but that would be
too easy. I can dump pieces of the repo so I will work on piecing it
back together from that unless someone else has any better suggestions.

Would you be willing to make the repository available for some
post-mortem? The upside for you is that perhaps a developer could fix
it by hand. The upside for us would be fixing a potential problem.

Is this fsfs or bdb? Have you done anything to muck with any of the
files in the repository directly?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
 
This message (and any associated files) is intended only for the 
use of the individual or entity to which it is addressed and may 
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient 
you are hereby notified that any dissemination, copying or 
distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, 
please notify us immediately by replying to the message and deleting 
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Received on Thu Mar 15 20:58:31 2007

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.