db/current contents are wrong

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
Hi List,

Due to incorrect backups and a restore, my repository only goes up
to revision 242. However, we were at 553. The contents of
/repos/db/current are:

242 447 1z

But db/revs/ contains everything up through 553.

Is it possible to fix this situation? 'svnadmin verify' reports no
problems, but only goes up to 242.

I would suggest (mainly because Max Bowsher suggested it on IRC, and
Max is really smart ;-) changing that first 242 to 553, then dumping
the contents of the repository and reloading into a new repository,
that'll ensure that the other two numbers in the current file are
correct.

Also, be sure to work from a copy of your repository, just in case you
screw up and need to start over.
-garrett

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Wed, 14 Jun 2006, Garrett Rooney wrote:

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
>Hi List,
>
>Due to incorrect backups and a restore, my repository only goes up
>to revision 242. However, we were at 553. The contents of
>/repos/db/current are:
>
>242 447 1z
>
>But db/revs/ contains everything up through 553.
>
>Is it possible to fix this situation? 'svnadmin verify' reports
>no problems, but only goes up to 242.
>
I would suggest (mainly because Max Bowsher suggested it on IRC,
and Max is really smart ;-) changing that first 242 to 553, then
dumping the contents of the repository and reloading into a new
repository, that'll ensure that the other two numbers in the
current file are correct.

Also, be sure to work from a copy of your repository, just in case
you screw up and need to start over.

That sort-of worked. Changing the 242 to 553 and dumping dumped
everything up to 553. It appeared to work. When I tried the
'svnadmin load' command I could not get it to work.

So, I just changed the 242 to 553, then did a checkout, edited a
file, and checked it back in, and it worked.

Thanks (and thanks to Max too!)

-k.

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
Wed, 14 Jun 2006, Garrett Rooney wrote:

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
>Hi List,
>>
>Due to incorrect backups and a restore, my repository only goes up
>to revision 242. However, we were at 553. The contents of
>/repos/db/current are:
>>
>242 447 1z
>>
>But db/revs/ contains everything up through 553.
>>
>Is it possible to fix this situation? 'svnadmin verify' reports
>no problems, but only goes up to 242.
>
I would suggest (mainly because Max Bowsher suggested it on IRC,
and Max is really smart ;-) changing that first 242 to 553, then
dumping the contents of the repository and reloading into a new
repository, that'll ensure that the other two numbers in the
current file are correct.

Also, be sure to work from a copy of your repository, just in case
you screw up and need to start over.

That sort-of worked. Changing the 242 to 553 and dumping dumped
everything up to 553. It appeared to work. When I tried the
'svnadmin load' command I could not get it to work.

Uhh, can you be more specific? It should work.

So, I just changed the 242 to 553, then did a checkout, edited a
file, and checked it back in, and it worked.

That's really not safe to do. Those other entries in the current file
are important, and if you continue to make changes while they're
potentially out of date you risk ending up with a repository that
won't work.
-garrett

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Wed, 14 Jun 2006, Garrett Rooney wrote:

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
>Wed, 14 Jun 2006, Garrett Rooney wrote:
>
>6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
>>Hi List,
>>>
>>Due to incorrect backups and a restore, my repository only
>>goes up to revision 242. However, we were at 553. The contents
>>of /repos/db/current are:
>>>
>>242 447 1z
>>>
>>But db/revs/ contains everything up through 553.
>>>
>>Is it possible to fix this situation? 'svnadmin verify'
>>reports no problems, but only goes up to 242.
>>
>I would suggest (mainly because Max Bowsher suggested it on
>IRC, and Max is really smart ;-) changing that first 242 to
>553, then dumping the contents of the repository and reloading
>into a new repository, that'll ensure that the other two
>numbers in the current file are correct.
>>
>Also, be sure to work from a copy of your repository, just in
>case you screw up and need to start over.
>
>That sort-of worked. Changing the 242 to 553 and dumping dumped
>everything up to 553. It appeared to work. When I tried the
>'svnadmin load' command I could not get it to work.
>
Uhh, can you be more specific? It should work.

After I dump, to I do anything to the (possibly corrupted)
repository?

If I delete it, it complains that it cannot find files. If I don't
delet it, I get this:

$ svnadmin load /opt/svn/repos/ < ./svn_dump
<<< Started new transaction, based on original revision 1
* adding path : 4D done.
svnadmin: File already exists: filesystem '/opt/svn/repos/db',
transaction '553-2', path 'EVA'
* adding path : EVA $

-k.

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:

After I dump, to I do anything to the (possibly corrupted)
repository?

If I delete it, it complains that it cannot find files. If I don't
delet it, I get this:

$ svnadmin load /opt/svn/repos/ < ./svn_dump
<<< Started new transaction, based on original revision 1
* adding path : 4D done.
svnadmin: File already exists: filesystem '/opt/svn/repos/db',
transaction '553-2', path 'EVA'
* adding path : EVA $

Ahh, ok, what you're supposed to do is create a new, emtpy repository
and load the dump into it. Then you'll have an exact copy of your old
repository you can move into place and use.
-garrett

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org

Wed, 14 Jun 2006, Garrett Rooney wrote:

6/14/06, Ken Mankoff <mankoff (AT) gmail (DOT) comwrote:
>
>After I dump, to I do anything to the (possibly corrupted)
>repository?
>
>If I delete it, it complains that it cannot find files. If I don't
>delet it, I get this:
>
>$ svnadmin load /opt/svn/repos/ < ./svn_dump
><<< Started new transaction, based on original revision 1
>* adding path : 4D done.
>svnadmin: File already exists: filesystem '/opt/svn/repos/db',
>transaction '553-2', path 'EVA'
>* adding path : EVA $
>
Ahh, ok, what you're supposed to do is create a new, emtpy repository
and load the dump into it. Then you'll have an exact copy of your old
repository you can move into place and use.

K, that worked perfectly. Thank you! Very much!

-k.

To unsubscribe, e-mail: users-unsubscribe (AT) subversion (DOT) tigris.org
For additional commands, e-mail: users-help (AT) subversion (DOT) tigris.org