You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Michael Johns <mi...@clear2pay.com> on 2008/01/09 01:57:51 UTC

Missing rev file

I've seen a handful of posts around the web regarding this issue, but I've yet to find anyone who has successfully conquered it.  I'm hoping I can find such a brilliant mind here.

One of the revisions in my repository is missing.  It's revision 2521, to be exact.  And by "missing," I mean that the db\revs\2521 file flat-out doesn't exist.  Why?  I don't know, and I've taken steps to make sure it doesn't happen again, but I'm still left with this one missing revision.  This is causing a handful of problems, none of which are affecting our usage of the repository, but all of which I'd like resolved.

I don't care too much about recovering the contents of this revision.  I know more or less what was in there, and I have copies of that data I can commit again if need be.  What I do care about is cleaning up the problem so I can produce a clean backup of the repository.  As it stands now, a dump fails at 2521, for obvious reasons.

I've tried "spoofing" the revision by copying other rev files and modifying them to look like 2521.  By doing this, I can get a dump (and a verify) to proceed past 2521, but it always fails later on down the line, presumably on a revision that depends on 2521.

Is there any way at all to trick SVN into thinking that revision exists so I can dump the entire repository?  Again, I don't care one bit if the data is valid; I just want the dump to complete.  Because the revision doesn't exist at all, excellent tools such as fsfsverify won't help me.

Any and all insight will be appreciated.

Much Thanks,
Michael

RE: RE: Missing rev file

Posted by "Srilakshmanan, Lakshman" <la...@police.vic.gov.au>.
Hi Michael,
 
The reason I am interested in your problem is because I am about to
setup a Subversion repository identical to your configuration.
 
Have you reviewed your backup ? 
Does this revision exist in your backup ? , If it does have you tried to
copy it from backup into your production repository ?
 
Thanks
Lakshman

________________________________

From: Michael Johns [mailto:michael.johns@clear2pay.com] 
Sent: Wednesday, 9 January 2008 1:24 PM
To: Srilakshmanan, Lakshman
Cc: users@subversion.tigris.org
Subject: RE: Missing rev file



1.     1.4.5

2.     Windows Server 2003

3.     https

4.     local file system on server

 

 

From: Srilakshmanan, Lakshman
[mailto:lakshman.srilakshmanan@police.vic.gov.au] 
Sent: Tuesday, January 08, 2008 9:21 PM
To: Michael Johns
Cc: users@subversion.tigris.org
Subject: RE: Missing rev file

 

Hi Michael,

 

I am sorry I can't resolve your problem, but could you please provide
the following

1) svn version

2) OS

3) access method used(http, svn, file)

4) is your repository on a network share or local to svn server.

 

Thanks

Lakshman

________________________________

From: Michael Johns [mailto:michael.johns@clear2pay.com] 
Sent: Wednesday, 9 January 2008 12:58 PM
To: users@subversion.tigris.org
Subject: Missing rev file

I've seen a handful of posts around the web regarding this issue, but
I've yet to find anyone who has successfully conquered it.  I'm hoping I
can find such a brilliant mind here.

 

One of the revisions in my repository is missing.  It's revision 2521,
to be exact.  And by "missing," I mean that the db\revs\2521 file
flat-out doesn't exist.  Why?  I don't know, and I've taken steps to
make sure it doesn't happen again, but I'm still left with this one
missing revision.  This is causing a handful of problems, none of which
are affecting our usage of the repository, but all of which I'd like
resolved.

 

I don't care too much about recovering the contents of this revision.  I
know more or less what was in there, and I have copies of that data I
can commit again if need be.  What I do care about is cleaning up the
problem so I can produce a clean backup of the repository.  As it stands
now, a dump fails at 2521, for obvious reasons.

 

I've tried "spoofing" the revision by copying other rev files and
modifying them to look like 2521.  By doing this, I can get a dump (and
a verify) to proceed past 2521, but it always fails later on down the
line, presumably on a revision that depends on 2521.

 

Is there any way at all to trick SVN into thinking that revision exists
so I can dump the entire repository?  Again, I don't care one bit if the
data is valid; I just want the dump to complete.  Because the revision
doesn't exist at all, excellent tools such as fsfsverify won't help me.

 

Any and all insight will be appreciated.

 

Much Thanks,

Michael

 
========================================================================
========================
EMAIL DISCLAIMER
 
This email and any attachments are confidential. They may also be
subject to copyright.
 
If you are not an intended recipient of this email please immediately
contact us by replying
to this email and then delete this email. 
 
You must not read, use, copy, retain, forward or disclose this email or
any attachment.
 
We do not accept any liability arising from or in connection with
unauthorised use or disclosure 
of the information contained in this email or any attachment.
 
We make reasonable efforts to protect against computer viruses but we do
not accept liability
for any liability, loss or damage caused by any computer virus contained
in this email.
========================================================================
========================

================================================================================================
EMAIL DISCLAIMER

This email and any attachments are confidential. They may also be subject to copyright.

If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email. 

You must not read, use, copy, retain, forward or disclose this email or any attachment.

We do not accept any liability arising from or in connection with unauthorised use or disclosure 
of the information contained in this email or any attachment.

We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.
================================================================================================

RE: Missing rev file

Posted by Michael Johns <mi...@clear2pay.com>.
1.     1.4.5

2.     Windows Server 2003

3.     https

4.     local file system on server


From: Srilakshmanan, Lakshman [mailto:lakshman.srilakshmanan@police.vic.gov.au]
Sent: Tuesday, January 08, 2008 9:21 PM
To: Michael Johns
Cc: users@subversion.tigris.org
Subject: RE: Missing rev file

Hi Michael,

I am sorry I can't resolve your problem, but could you please provide the following
1) svn version
2) OS
3) access method used(http, svn, file)
4) is your repository on a network share or local to svn server.

Thanks
Lakshman
________________________________
From: Michael Johns [mailto:michael.johns@clear2pay.com]
Sent: Wednesday, 9 January 2008 12:58 PM
To: users@subversion.tigris.org
Subject: Missing rev file
I've seen a handful of posts around the web regarding this issue, but I've yet to find anyone who has successfully conquered it.  I'm hoping I can find such a brilliant mind here.

One of the revisions in my repository is missing.  It's revision 2521, to be exact.  And by "missing," I mean that the db\revs\2521 file flat-out doesn't exist.  Why?  I don't know, and I've taken steps to make sure it doesn't happen again, but I'm still left with this one missing revision.  This is causing a handful of problems, none of which are affecting our usage of the repository, but all of which I'd like resolved.

I don't care too much about recovering the contents of this revision.  I know more or less what was in there, and I have copies of that data I can commit again if need be.  What I do care about is cleaning up the problem so I can produce a clean backup of the repository.  As it stands now, a dump fails at 2521, for obvious reasons.

I've tried "spoofing" the revision by copying other rev files and modifying them to look like 2521.  By doing this, I can get a dump (and a verify) to proceed past 2521, but it always fails later on down the line, presumably on a revision that depends on 2521.

Is there any way at all to trick SVN into thinking that revision exists so I can dump the entire repository?  Again, I don't care one bit if the data is valid; I just want the dump to complete.  Because the revision doesn't exist at all, excellent tools such as fsfsverify won't help me.

Any and all insight will be appreciated.

Much Thanks,
Michael



================================================================================================

EMAIL DISCLAIMER



This email and any attachments are confidential. They may also be subject to copyright.



If you are not an intended recipient of this email please immediately contact us by replying

to this email and then delete this email.



You must not read, use, copy, retain, forward or disclose this email or any attachment.



We do not accept any liability arising from or in connection with unauthorised use or disclosure

of the information contained in this email or any attachment.



We make reasonable efforts to protect against computer viruses but we do not accept liability

for any liability, loss or damage caused by any computer virus contained in this email.

================================================================================================

RE: Missing rev file

Posted by "Srilakshmanan, Lakshman" <la...@police.vic.gov.au>.
Hi Michael,
 
I am sorry I can't resolve your problem, but could you please provide
the following
1) svn version
2) OS
3) access method used(http, svn, file)
4) is your repository on a network share or local to svn server.
 
Thanks
Lakshman
________________________________

From: Michael Johns [mailto:michael.johns@clear2pay.com] 
Sent: Wednesday, 9 January 2008 12:58 PM
To: users@subversion.tigris.org
Subject: Missing rev file



I've seen a handful of posts around the web regarding this issue, but
I've yet to find anyone who has successfully conquered it.  I'm hoping I
can find such a brilliant mind here.

 

One of the revisions in my repository is missing.  It's revision 2521,
to be exact.  And by "missing," I mean that the db\revs\2521 file
flat-out doesn't exist.  Why?  I don't know, and I've taken steps to
make sure it doesn't happen again, but I'm still left with this one
missing revision.  This is causing a handful of problems, none of which
are affecting our usage of the repository, but all of which I'd like
resolved.

 

I don't care too much about recovering the contents of this revision.  I
know more or less what was in there, and I have copies of that data I
can commit again if need be.  What I do care about is cleaning up the
problem so I can produce a clean backup of the repository.  As it stands
now, a dump fails at 2521, for obvious reasons.

 

I've tried "spoofing" the revision by copying other rev files and
modifying them to look like 2521.  By doing this, I can get a dump (and
a verify) to proceed past 2521, but it always fails later on down the
line, presumably on a revision that depends on 2521.

 

Is there any way at all to trick SVN into thinking that revision exists
so I can dump the entire repository?  Again, I don't care one bit if the
data is valid; I just want the dump to complete.  Because the revision
doesn't exist at all, excellent tools such as fsfsverify won't help me.

 

Any and all insight will be appreciated.

 

Much Thanks,

Michael


================================================================================================
EMAIL DISCLAIMER

This email and any attachments are confidential. They may also be subject to copyright.

If you are not an intended recipient of this email please immediately contact us by replying
to this email and then delete this email. 

You must not read, use, copy, retain, forward or disclose this email or any attachment.

We do not accept any liability arising from or in connection with unauthorised use or disclosure 
of the information contained in this email or any attachment.

We make reasonable efforts to protect against computer viruses but we do not accept liability
for any liability, loss or damage caused by any computer virus contained in this email.
================================================================================================