You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kamaraju S Kusumanchi <ka...@bluebottle.com> on 2007/09/04 00:41:02 UTC
recovering a repository
Hi all
I have a subversion repository which I haven't touched for a while.
Today I tried to work on of the projects this repository used to contain.
To my dismay, I found that the repository is not working. I think the
repository is corrupted but I am not sure if that is in fact the case. Can
someone please help me? I am in panic mode right now!
My repository location is /home/rajulocal/src/repos
Currently, I have
$ls -alrt src/repos/
total 36
-rw-r--r-- 1 rajulocal rajulocal 229 2006-04-30 01:36 README.txt
drwxr-xr-x 2 rajulocal rajulocal 4096 2006-04-30 01:36 locks/
drwxr-xr-x 2 rajulocal rajulocal 4096 2006-04-30 01:36 hooks/
-r--r--r-- 1 rajulocal rajulocal 2 2006-04-30 01:36 format
drwxr-xr-x 2 rajulocal rajulocal 4096 2006-04-30 01:36 dav/
drwxr-xr-x 2 rajulocal rajulocal 4096 2006-04-30 01:36 conf/
drwxr-xr-x 7 rajulocal rajulocal 4096 2006-04-30 01:36 ../
drwxr-xr-x 7 rajulocal rajulocal 4096 2007-09-03 19:56 ./
drwxr-sr-x 5 rajulocal rajulocal 4096 2007-09-03 20:11 db/
$ls /home/rajulocal/src/repos/db/revs/
0 100 103 106 109 111 114 117 12 122 125 128 130 14 17 2
22 25 28 30 33 36 39 41 44 47 5 52 55 58 60 63 66 69 71
74 77 8 82 85 88 90 93 96 99
1 101 104 107 11 112 115 118 120 123 126 129 131 15 18 20
23 26 29 31 34 37 4 42 45 48 50 53 56 59 61 64 67 7 72
75 78 80 83 86 89 91 94 97
10 102 105 108 110 113 116 119 121 124 127 13 132 16 19 21
24 27 3 32 35 38 40 43 46 49 51 54 57 6 62 65 68 70 73
76 79 81 84 87 9 92 95 98
However, If I do
$svn list file:///home/rajulocal/src/repos/
then there is no output.
Let's say this used to contain a project called pipe_flow. I had a working
copy of this project in ~/work/pipe_flow. From ~/work/pipe_flow , If I do
$cd ~/work/pipe_flow
$svn st -u
I see output such as
M * 131 variables.F90
However I do
$svn log variables.F90
svn: No such revision 131
$svn update
svn: Target path does not exist
I also tried copying /home/rajulocal/src/repos to a temp directory and
execute
$svnadmin recover /home/rajulocal/temp/
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 0.
Does this mean that I somehow corrupted the repository? Is there any way I
can recover my project? Any help is very much appreciated.
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Clemens <cl...@thalesgroup.com>.
Kamaraju S Kusumanchi wrote:
(...)
> So it seems now it is working upto revision 124. Any idea how to get
> further?
I see that others already gave you a helping hand. I could not add
anything other helpful to that said by them. So best is to follow what
Ryan proposed.
Cross the fingers and hope :-)
> Thanks for all the help, Clemens.
It was not much I could do. But I am glad it helped a bit at least. :-)
> raju
Clemens.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Ryan Schmidt wrote:
>
> On Sep 4, 2007, at 08:47, Kamaraju S Kusumanchi wrote:
>
>> Clemens wrote:
>>> I have examined your filenames in db/revs and they seem to be
>>> complete
>>> (namewise). What does your file
>>>
>>> db/current
>>>
>>> contain?
>>>
>>
>> $cat /home/rajulocal/src/repos/db/current
>> # This vi
>
> That's clearly busted. How did it get that way? Did you have hard
> disk corruption at some point? Do you have hard disk corruption right
> now? Do you have backups from which you can restore?
>
Yes. I had noticed some hard drive seek errors at some point and immediately
replaced the hard drive. This happened around Feb 2007. I didn't notice any
data loss at that time, so just copied the old hard drive's contents to new
hard drive.
>> $svnadmin verify /home/rajulocal/src/repos/
>> * Verified revision 0.
>> * Verified revision 1.
>> * Verified revision 2.
>> * Verified revision 3.
>> * Verified revision 4.
>> * Verified revision 5.
>> * Verified revision 6.
>> * Verified revision 7.
>> .....
>> * Verified revision 119.
>> * Verified revision 120.
>> * Verified revision 121.
>> * Verified revision 122.
>> * Verified revision 123.
>> * Verified revision 124.
>> svnadmin: Revision file lacks trailing newline
>>
>> So it seems now it is working upto revision 124. Any idea how to get
>> further?
>
> Do you have a backup of the 124 file you could restore? If not, what
> is the contents of the 124 file now? Does it look reasonable (that
> is, does it look similar in shape to the content of the previous
> revision files that verified correctly)?
The revision 124 file was created on
$ls -al 124
-rw-r--r-- 1 rajulocal rajulocal 8755 2006-11-04 22:04 124
I make regular backup of the hard drive by synchronizing the files on this
computer with an external USB drive. So all I have is a mirror of my
current hard drive not a backup of old files.
>
> Before you go making any other changes to your repository in an
> attempt to recover it, please make sure you back up the broken
> repository as it is now, in case our recovery attempts break it further.
I have a backup of the current repository. Any suggestions on how to
proceed?
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 5, 2007, at 07:21, Bicking, David (HHoldings, IT) wrote:
>>> The contents of db/revs/124 look reasonable. However the contents of
>>> db/revs/125 is not good. It is basically a bunch of ^@. When I tried
>>> to cat it, nothing is printed on the command line. However the
>>> contents of db/revs/125, db/revs/126 etc., all look reasonable upto
>>> revision 132.
>>
>> In the future, make sure you back up your repository religiously.
>> Creating a backup in the post-commit hook is the best idea,
>> so that the backup gets created the instant the original gets
>> created, so there's no chance for any data loss.
>
> All this raises a question for me. Unless I misread something in the
> thread, the corruption happened somewhere in February, but was not
> discovered until recently. Thus, a robust backup schedule still would
> not be useful here.
>
> Are there any tools available to "analyze" the database? I would like
> to have a nightly process verify the integrity of the repository, log
> any problems, and return a useful exit code. This, combined with a
> reasonable backup rotation, should prevent this problem from occuring.
> Ideally, the revision numbers (and user ids) affected by corruption
> should be logged so the dump/reload solution could be quickly
> executed.
Don't forget to Reply To All so your reply goes to the mailing list
too, not just to me.
The nice thing about FSFS repositories is that once created,
revisions never change. So the robust backup method is to backup the
revision files the moment they're created and retain them
indefinitely. If they ever become corrupted on the hard drive due to
hard drive controller failure or user error or what have you, restore
them from the immutable backup (CD, DVD, etc.).
Now, with "svn propset --revprop" you can change old revision
properlies. So it may be necessary to re-backup revprops if they change.
The tool to analyze the repo is "svnadmin verify"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 4, 2007, at 16:07, Kamaraju S Kusumanchi wrote:
> Ryan Schmidt wrote:
>
>>>>> I do not know for sure what it should contain, but something
>>>>> around
>>>>
>>>> 132 d 1
>>>>
>>>> would be a good content perhaps. If it does not contain this
>>>> contents,
>>>> perhaps try to modify it and retry svnadmin verify ...
>>>
>>> Now when I changed it to
>>>
>>> $svnadmin verify /home/rajulocal/src/repos/
>>> * Verified revision 0.
>>> * Verified revision 1.
>>> * Verified revision 2.
>>> * Verified revision 3.
>>> * Verified revision 4.
>>> * Verified revision 5.
>>> * Verified revision 6.
>>> * Verified revision 7.
>>> .....
>>> * Verified revision 119.
>>> * Verified revision 120.
>>> * Verified revision 121.
>>> * Verified revision 122.
>>> * Verified revision 123.
>>> * Verified revision 124.
>>> svnadmin: Revision file lacks trailing newline
>>>
>>> So it seems now it is working upto revision 124. Any idea how to get
>>> further?
>>
>> Do you have a backup of the 124 file you could restore? If not, what
>> is the contents of the 124 file now? Does it look reasonable (that
>> is, does it look similar in shape to the content of the previous
>> revision files that verified correctly)?
>>
>
> The contents of db/revs/124 look reasonable. However the contents of
> db/revs/125 is not good. It is basically a bunch of ^@. When I
> tried to cat
> it, nothing is printed on the command line. However the contents of
> db/revs/125, db/revs/126 etc., all look reasonable upto revision 132.
Oh, yes, sorry, of course, it said it verified revision 124, and then
it threw an error, so yes, revision 125 is the one it's complaining
about. And you've discovered it's corrupted and you have no backup.
So now you have a problem.
Subversion stores revisions as deltas against previous revisions.
Hopefully, none of your revisions 126 thru 132 depend on revision
125. (The skip-deltas algorithm determines which previous revision is
used for the delta.) And hopefully the information you committed in
revision 125 wasn't important, because it's gone now.
The only "solution" I can think of is to "svnadmin dump" revisions 0
thru 124, and 126 thru 132, "svnadmin create" new repository,
"svnadmin load" the first dumpfile and then the second dumpfile into
the new repository. Then check out new working copies from the new
repository. You should now have a repository which is not corrupted,
but it won't contain anything from revision 125.
If you still have old working copies from the old repository, you
could compare them (using external diff utilities) to the contents of
a fresh checkout from the new repository. If there are any
differences, perhaps those are the differences that were lost in
r125, and you could re-do those changes in the new working copy and
commit them as a new revision, thus saving what was in r125.
In the future, make sure you back up your repository religiously.
Creating a backup in the post-commit hook is the best idea, so that
the backup gets created the instant the original gets created, so
there's no chance for any data loss.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Ryan Schmidt wrote:
> >>> I do not know for sure what it should contain, but something around
>>>
>>> 132 d 1
>>>
>>> would be a good content perhaps. If it does not contain this
>>> contents,
>>> perhaps try to modify it and retry svnadmin verify ...
>>
>> Now when I changed it to
>>
>> $svnadmin verify /home/rajulocal/src/repos/
>> * Verified revision 0.
>> * Verified revision 1.
>> * Verified revision 2.
>> * Verified revision 3.
>> * Verified revision 4.
>> * Verified revision 5.
>> * Verified revision 6.
>> * Verified revision 7.
>> .....
>> * Verified revision 119.
>> * Verified revision 120.
>> * Verified revision 121.
>> * Verified revision 122.
>> * Verified revision 123.
>> * Verified revision 124.
>> svnadmin: Revision file lacks trailing newline
>>
>> So it seems now it is working upto revision 124. Any idea how to get
>> further?
>
> Do you have a backup of the 124 file you could restore? If not, what
> is the contents of the 124 file now? Does it look reasonable (that
> is, does it look similar in shape to the content of the previous
> revision files that verified correctly)?
>
The contents of db/revs/124 look reasonable. However the contents of
db/revs/125 is not good. It is basically a bunch of ^@. When I tried to cat
it, nothing is printed on the command line. However the contents of
db/revs/125, db/revs/126 etc., all look reasonable upto revision 132.
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 4, 2007, at 08:47, Kamaraju S Kusumanchi wrote:
> Clemens wrote:
>> I have examined your filenames in db/revs and they seem to be
>> complete
>> (namewise). What does your file
>>
>> db/current
>>
>> contain?
>>
>
> $cat /home/rajulocal/src/repos/db/current
> # This vi
That's clearly busted. How did it get that way? Did you have hard
disk corruption at some point? Do you have hard disk corruption right
now? Do you have backups from which you can restore?
>> I do not know for sure what it should contain, but something around
>>
>> 132 d 1
>>
>> would be a good content perhaps. If it does not contain this
>> contents,
>> perhaps try to modify it and retry svnadmin verify ...
>
> Now when I changed it to
>
> $svnadmin verify /home/rajulocal/src/repos/
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> * Verified revision 3.
> * Verified revision 4.
> * Verified revision 5.
> * Verified revision 6.
> * Verified revision 7.
> .....
> * Verified revision 119.
> * Verified revision 120.
> * Verified revision 121.
> * Verified revision 122.
> * Verified revision 123.
> * Verified revision 124.
> svnadmin: Revision file lacks trailing newline
>
> So it seems now it is working upto revision 124. Any idea how to get
> further?
Do you have a backup of the 124 file you could restore? If not, what
is the contents of the 124 file now? Does it look reasonable (that
is, does it look similar in shape to the content of the previous
revision files that verified correctly)?
Before you go making any other changes to your repository in an
attempt to recover it, please make sure you back up the broken
repository as it is now, in case our recovery attempts break it further.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Clemens wrote:
> I have examined your filenames in db/revs and they seem to be complete
> (namewise). What does your file
>
> db/current
>
> contain?
>
$cat /home/rajulocal/src/repos/db/current
# This vi
> I do not know for sure what it should contain, but something around
>
> 132 d 1
>
> would be a good content perhaps. If it does not contain this contents,
> perhaps try to modify it and retry svnadmin verify ...
Now when I changed it to
$svnadmin verify /home/rajulocal/src/repos/
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
* Verified revision 7.
.....
* Verified revision 119.
* Verified revision 120.
* Verified revision 121.
* Verified revision 122.
* Verified revision 123.
* Verified revision 124.
svnadmin: Revision file lacks trailing newline
So it seems now it is working upto revision 124. Any idea how to get
further?
Thanks for all the help, Clemens.
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Clemens <cl...@thalesgroup.com>.
Kamaraju S Kusumanchi wrote:
(...)
> I am getting
>
> $svnadmin verify /home/rajulocal/src/repos/
> * Verified revision 0.
>
> Does this mean that it is complaining or does it mean that only
> revision 0 is recoverable.
Hmmm ... I would interpret this as, there is only a revision 0 available
at all.
This is strange, as all the other revision (up to 132) are laying around
in db/revs though ... :-/
> I searched the archives for a while. But I am getting lots of hits
> most of which seem irrelevant to my problem.
>
> Any other suggestions?
I have examined your filenames in db/revs and they seem to be complete
(namewise). What does your file
db/current
contain?
I do not know for sure what it should contain, but something around
132 d 1
would be a good content perhaps. If it does not contain this contents,
perhaps try to modify it and retry svnadmin verify ...
Beside these, I have no real idea what else is going on ... sorry!
Ciao,
Clemens.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 4, 2007, at 08:49, Kamaraju S Kusumanchi wrote:
> Rainer Sokoll wrote:
>
>> You may provide more information: which svn version do you use? Which
>> backend (fsfs or bdb)?
>
> I am not sure which backend I am using. How can I find out? I am
> using the
> default version that comes with Debian, Stable (Etch). However the
> repository has been created long back. Even then I was using the
> default
> version that came with Debian.
The contents of the file db/fs-type in the repository will tell you
what kind of repository it is, but the fact that you have individual
files for each revision in db/revs already tells us this is an FSFS
repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Rainer Sokoll wrote:
> On Tue, Sep 04, 2007 at 02:16:57AM -0400, Kamaraju S Kusumanchi wrote:
>> Clemens wrote:
>
>> > Hmmm ... the first thing I would try is
>> >
>> > svnadmin verify /home/rajulocal/src/repos/
>
>> I am getting
>>
>> $svnadmin verify /home/rajulocal/src/repos/
>> * Verified revision 0.
>>
>> Does this mean that it is complaining or does it mean that only revision
>> 0 is recoverable.
>
> I would think so. Can you dump the repo? If not, most probably your repo
> is damaged.
> You may provide more information: which svn version do you use? Which
> backend (fsfs or bdb)?
$svn --version
svn, version 1.4.2 (r22196)
compiled Nov 10 2006, 17:39:50
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet
(http://www.Collab.Net/).
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
I am not sure which backend I am using. How can I find out? I am using the
default version that comes with Debian, Stable (Etch). However the
repository has been created long back. Even then I was using the default
version that came with Debian.
regards
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Rainer Sokoll <R....@intershop.de>.
On Tue, Sep 04, 2007 at 02:16:57AM -0400, Kamaraju S Kusumanchi wrote:
> Clemens wrote:
> > Hmmm ... the first thing I would try is
> >
> > svnadmin verify /home/rajulocal/src/repos/
> I am getting
>
> $svnadmin verify /home/rajulocal/src/repos/
> * Verified revision 0.
>
> Does this mean that it is complaining or does it mean that only revision 0
> is recoverable.
I would think so. Can you dump the repo? If not, most probably your repo
is damaged.
You may provide more information: which svn version do you use? Which
backend (fsfs or bdb)?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Clemens wrote:
>
>
> Kamaraju S Kusumanchi wrote:
>> Hi all
>
> Hi too,
>
>> I have a subversion repository which I haven't touched for a while.
>> Today I tried to work on of the projects this repository used to contain.
>> To my dismay, I found that the repository is not working. I think the
>> repository is corrupted but I am not sure if that is in fact the case.
>> Can someone please help me? I am in panic mode right now!
>
> (...)
>
>> $svn list file:///home/rajulocal/src/repos/
>
> Hmmm ... the first thing I would try is
>
> svnadmin verify /home/rajulocal/src/repos/
>
> and looking to its output. If it complains, you may search this mailing
> list for hints how to recover. But be prepared, that recovering from a
> repository that svnadmin verify reports to be bad, may not be possible
> at all.
>
I am getting
$svnadmin verify /home/rajulocal/src/repos/
* Verified revision 0.
Does this mean that it is complaining or does it mean that only revision 0
is recoverable. I searched the archives for a while. But I am getting lots
of hits most of which seem irrelevant to my problem.
Any other suggestions?
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Clemens <cl...@thalesgroup.com>.
Kamaraju S Kusumanchi wrote:
> Hi all
Hi too,
> I have a subversion repository which I haven't touched for a while.
> Today I tried to work on of the projects this repository used to contain.
> To my dismay, I found that the repository is not working. I think the
> repository is corrupted but I am not sure if that is in fact the case. Can
> someone please help me? I am in panic mode right now!
(...)
> $svn list file:///home/rajulocal/src/repos/
Hmmm ... the first thing I would try is
svnadmin verify /home/rajulocal/src/repos/
and looking to its output. If it complains, you may search this mailing
list for hints how to recover. But be prepared, that recovering from a
repository that svnadmin verify reports to be bad, may not be possible
at all.
(...)
svnadmin recover seems only to be able to recover Berkley DB type
repositories. But your one seems to be a fsfs type one.
Ciao,
Clemens.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Neil Martinsen-Burrell wrote:
>
> It would appear that the root directory of your project contains no files.
> Can you do
>
> svn log -v file:///home/rajulocal/src/repos
>
> to see if perhaps the files were deleted in some revision? You can also
> do
>
> svn info file:///home/rajulocal/src/repos
>
> to see what information the subversion client is able to extract from the
> repository. In particular, this will tell you the overall revision number
> of the repository.
Initially my db/current file is
# This vi
With this I get
$svn log -v file:///home/rajulocal/src/repos/
------------------------------------------------------------------------
$svn info file:///home/rajulocal/src/repos/
Path: repos
URL: file:///home/rajulocal/src/repos
Repository Root: file:///home/rajulocal/src/repos
Repository UUID: 4b491453-9f12-0410-a375-f21ff25ee2d8
Revision: 0
Node Kind: directory
Last Changed Rev: 0
Last Changed Date: 2006-04-30 01:36:49 -0400 (Sun, 30 Apr 2006)
When I changed the db/current file to
132 d 1
the output of svn log -v is
http://pastebin.com/m124d0abf
the output of svn info is
$svn info file:///home/rajulocal/src/repos/
Path: repos
URL: file:///home/rajulocal/src/repos
Repository Root: file:///home/rajulocal/src/repos
Repository UUID: 4b491453-9f12-0410-a375-f21ff25ee2d8
Revision: 132
Node Kind: directory
Last Changed Author: rajulocal
Last Changed Rev: 132
Last Changed Date: 2007-02-09 01:41:10 -0500 (Fri, 09 Feb 2007)
>
>> Let's say this used to contain a project called pipe_flow. I had a
>> working copy of this project in ~/work/pipe_flow. From ~/work/pipe_flow ,
>> If I do
>>
>> $cd ~/work/pipe_flow
>> $svn st -u
>>
>> I see output such as
>> M * 131 variables.F90
>
> Can you show us the full output of this command?
It's a bit long. So I pasted it in
http://pastebin.com/m7bed1573
>
>> However I do
>> $svn log variables.F90
>> svn: No such revision 131
>>
>> $svn update
>> svn: Target path does not exist
>
> I do not know what is happening here. If you send more information,
> perhaps we can figure it out.
>
I actually do not know what information I should send. If there is any other
information required, I would be glad to provide.
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Neil Martinsen-Burrell <nm...@wartburg.edu>.
Kamaraju S Kusumanchi <kamaraju <at> bluebottle.com> writes:
> I have a subversion repository which I haven't touched for a while.
> Today I tried to work on of the projects this repository used to contain.
> To my dismay, I found that the repository is not working. I think the
> repository is corrupted but I am not sure if that is in fact the case. Can
> someone please help me? I am in panic mode right now!
>
> My repository location is /home/rajulocal/src/repos
[...]
> However, If I do
>
> $svn list file:///home/rajulocal/src/repos/
>
> then there is no output.
It would appear that the root directory of your project contains no files. Can
you do
svn log -v file:///home/rajulocal/src/repos
to see if perhaps the files were deleted in some revision? You can also do
svn info file:///home/rajulocal/src/repos
to see what information the subversion client is able to extract from the
repository. In particular, this will tell you the overall revision number of
the repository.
> Let's say this used to contain a project called pipe_flow. I had a working
> copy of this project in ~/work/pipe_flow. From ~/work/pipe_flow , If I do
>
> $cd ~/work/pipe_flow
> $svn st -u
>
> I see output such as
> M * 131 variables.F90
Can you show us the full output of this command?
> However I do
> $svn log variables.F90
> svn: No such revision 131
>
> $svn update
> svn: Target path does not exist
I do not know what is happening here. If you send more information, perhaps we
can figure it out.
-Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: recovering a repository
Posted by Kamaraju S Kusumanchi <ka...@bluebottle.com>.
Kamaraju S Kusumanchi wrote:
> Hi all
>
> I have a subversion repository which I haven't touched for a while.
> Today I tried to work on of the projects this repository used to contain.
> To my dismay, I found that the repository is not working. I think the
> repository is corrupted but I am not sure if that is in fact the case. Can
> someone please help me? I am in panic mode right now!
>
I would like to thank Clemens, Ryan Schmidt, Rainer Sokoll, Neil
Martinsen-Burrell (and other if I missed any) whose timely help helped me a
lot. Using svnadmin dump, svnadmin load commands I was able to recover upto
124 versions. After changing the db/current file to
132 d 1
I was able to checkout a copy of revision 132. It worked even though there
is no revision file for 125. Plus I had a working copy revision 127 in the
backups (found this only after posting my previous emails). Using these
working copies (revisions 127, 132) I was able to recover almost all the
repository intact. I also found that none of the files in db/revprops were
corrupted. So I had access to changelogs and can verify it further.
At the end of the day, I am very happy to say that I recovered most of my
repositoy with your help. Now I migrated all the projects in this
repository to a new repository.
I still have to figure out how to write the post commit hooks so that an
automatic backup is created every time I update the repository. But that
can wait till tomorrow :-)
thanks
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org