You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Mark Bardsley <ma...@6sigmadc.com> on 2006/05/04 09:57:26 UTC
Missing revisions in FSFS repository
Hi
I have recently had to restore a Subversion repository from a backup
(which was created using hot-backup.py). It all looked OK at first, but
when we tried to commit something to the restored repository, it failed.
On examination of the repository, it turns out that files 3-9 and 30-99
are missing from the db/revs directory. So it looks as though something
has failed in the backup - we should obviously have checked the backup
before we really needed it ...
Anyway, my question is, is there anything I can do to recover from this
situation? For example, is there some way to dump revisions 100-HEAD
then load them into a new repository (so I would just lose the history
for revisions 1-99)? I've tried various svnadmin dump commands, but it
looks as though the absence of the earlier revisions means that I can't
dump the later ones.
My fallback position is to create a new repository from a working copy,
and lose all the history information - but I'd to avoid this if possible.
Thanks in advance for any help you can offer.
Regards,
Mark Bardsley
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Missing revisions in FSFS repository
Posted by Mark Bardsley <ma...@6sigmadc.com>.
Thanks for the reply, Ryan
Ryan Schmidt wrote:
> On May 4, 2006, at 11:57, Mark Bardsley wrote:
>
>> I have recently had to restore a Subversion repository from a backup
>> (which was created using hot-backup.py). It all looked OK at first,
>> but when we tried to commit something to the restored repository, it
>> failed. On examination of the repository, it turns out that files
>> 3-9 and 30-99 are missing from the db/revs directory. So it looks as
>> though something has failed in the backup - we should obviously have
>> checked the backup before we really needed it ...
>
>
> Yeow! That's absolutely awful.
>
> What is your HEAD revision? Is it less than 300? I'd be curious to
> know if 300-999 were also missing...
>
> What version of Subversion is this? What version of hot-backup.py?
> What's the server OS and version and the hardware?
>
Our HEAD revision is 207. We were running Subversion 1.1.4 on RHEL4. I'm
not actually pointing the finger at hot-backup.py - the backup actually
gets ftp'd to a remote disk, then written to DVD, so there are a few
stages where things could have gone wrong.
>
>> Anyway, my question is, is there anything I can do to recover from
>> this situation? For example, is there some way to dump revisions
>> 100-HEAD then load them into a new repository (so I would just lose
>> the history for revisions 1-99)? I've tried various svnadmin dump
>> commands, but it looks as though the absence of the earlier
>> revisions means that I can't dump the later ones.
>
>
> FSFS stores revisions as deltas to previous revisions, so if previous
> revisions are broken or gone, that does indeed cause big problems for
> accessing subsequent revisions...
>
>
>> My fallback position is to create a new repository from a working
>> copy, and lose all the history information - but I'd to avoid this
>> if possible.
>
>
> I don't have a good suggestion for you but I'd wait to see what
> others on the list suggest before doing anything drastic.
>
OK, thanks, I'll wait for a while to see if there are any other suggestions.
Mark
>
>
>
> ---------------------------------------------------------------------
> 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
Re: Missing revisions in FSFS repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On May 4, 2006, at 11:57, Mark Bardsley wrote:
> I have recently had to restore a Subversion repository from a
> backup (which was created using hot-backup.py). It all looked OK at
> first, but when we tried to commit something to the restored
> repository, it failed. On examination of the repository, it turns
> out that files 3-9 and 30-99 are missing from the db/revs
> directory. So it looks as though something has failed in the backup
> - we should obviously have checked the backup before we really
> needed it ...
Yeow! That's absolutely awful.
What is your HEAD revision? Is it less than 300? I'd be curious to
know if 300-999 were also missing...
What version of Subversion is this? What version of hot-backup.py?
What's the server OS and version and the hardware?
> Anyway, my question is, is there anything I can do to recover from
> this situation? For example, is there some way to dump revisions
> 100-HEAD then load them into a new repository (so I would just lose
> the history for revisions 1-99)? I've tried various svnadmin dump
> commands, but it looks as though the absence of the earlier
> revisions means that I can't dump the later ones.
FSFS stores revisions as deltas to previous revisions, so if previous
revisions are broken or gone, that does indeed cause big problems for
accessing subsequent revisions...
> My fallback position is to create a new repository from a working
> copy, and lose all the history information - but I'd to avoid this
> if possible.
I don't have a good suggestion for you but I'd wait to see what
others on the list suggest before doing anything drastic.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org