You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Tony Thompson <To...@stone-ware.com> on 2007/03/15 17:36:18 UTC
Unable to dump repository
I have gotten my repository into such a state that I cannot do an
"svnadmin dump" or "svnadmin verify". I get an error message back that
says:
svnadmin: Filesystem path 'tags/v5.1.0.2' is neither a file nor a
directory
This happened after I had an issue after I deleted a tagged revision out
of the repository. I have the tags/v5.1.0.2 directory back in the
repository but apparently something is already corrupted. I am still
able to do a hotcopy but that doesn't help me because the copy is
corrupted as well. I am using v1.4.3.
Is there a way I can repair the repository?
Thanks
Tony
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.
Re: Apache and SVN server on different machines?
Posted by Russ <rs...@istandfor.com>.
You can set up 2 apache servers and have one proxy requests to the other.
Russ
Sent wirelessly via BlackBerry from T-Mobile.
-----Original Message-----
From: "T. Nguyen" <pt...@yahoo.com>
Date: Fri, 16 Mar 2007 18:51:14
To:users@subversion.tigris.org
Subject: Apache and SVN server on different machines?
Hi All,
How to setup a SVN server (with apache2 + openssl) that allows users outside of network can connect to SVN host which is behind the firewall?
Is it possible to setup a apache2 in one server in DMZ and SVN server in another server which is behind the firewall?
I am looking forward your answers. Thanks in advance.
T.
----------------
We won't tell. Get more on shows you hate to love: <http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265
>
(and love to hate): Yahoo! TV's Guilty Pleasures list.: <http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265
>
Apache and SVN server on different machines?
Posted by "T. Nguyen" <pt...@yahoo.com>.
Hi All,
How to setup a SVN server (with apache2 + openssl) that allows users outside of network can connect to SVN host which is behind the firewall?
Is it possible to setup a apache2 in one server in DMZ and SVN server in another server which is behind the firewall?
I am looking forward your answers. Thanks in advance.
T.
---------------------------------
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
Re: Unable to dump repository
Posted by Mark Phippard <ma...@gmail.com>.
On 3/16/07, Tony Thompson <To...@stone-ware.com> wrote:
>
> Some more information about configuration and how the repository got into
> this state. We are using SVN through Apache with the SVN modules. We have
> a reverse proxy server sitting in front of the Apache server and are using
> the Tortoise client on developer workstations. Apparently the proxy server
> was the source of the corruption. I was able to go directly to the Apache
> server and not corrupt a new repository and also through another proxy and
> not corrupt the repository. So, a reboot of the proxy seemed to clear
> matters up.
>
> But, that concerns me a bit. To get it to corrupt, I could add 3 files to
> my working copy and use the tortoise client to commit them. It reported
> back that the three files had been committed but a check of the repository
> with the Tortoise repo browser showed that only two files were in the
> repository. I could not find any errors in the Apache access or error log
> that would indicate there was an issue committing files.
>
> Since the reboot, I can't reproduce the issue anymore so hopefully with
> that info and the bad repository I sent someone can come up with a good
> solution.
>
I entered an issue for you:
http://subversion.tigris.org/issues/show_bug.cgi?id=2744
You can get a tigris account and add yourself to the CC. If you still have
the bad proxy available, it might be helpful to capture the traffic between
the proxy and the server. The devs mentioned that on IRC.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
RE: Unable to dump repository
Posted by Tony Thompson <To...@stone-ware.com>.
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 <To...@stone-ware.com> wrote:
On 3/15/07, Tony Thompson < Tony.Thompson@stone-ware.com
<ma...@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.
RE: Unable to dump repository
Posted by Tony Thompson <To...@stone-ware.com>.
Some more information about configuration and how the repository got
into this state. We are using SVN through Apache with the SVN modules.
We have a reverse proxy server sitting in front of the Apache server and
are using the Tortoise client on developer workstations. Apparently the
proxy server was the source of the corruption. I was able to go
directly to the Apache server and not corrupt a new repository and also
through another proxy and not corrupt the repository. So, a reboot of
the proxy seemed to clear matters up.
But, that concerns me a bit. To get it to corrupt, I could add 3 files
to my working copy and use the tortoise client to commit them. It
reported back that the three files had been committed but a check of the
repository with the Tortoise repo browser showed that only two files
were in the repository. I could not find any errors in the Apache
access or error log that would indicate there was an issue committing
files.
Since the reboot, I can't reproduce the issue anymore so hopefully with
that info and the bad repository I sent someone can come up with a good
solution.
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 <To...@stone-ware.com> wrote:
On 3/15/07, Tony Thompson < Tony.Thompson@stone-ware.com
<ma...@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.
Re: Unable to dump repository
Posted by Mark Phippard <ma...@gmail.com>.
On 3/15/07, Tony Thompson <To...@stone-ware.com> wrote:
>
> On 3/15/07, Tony Thompson <To...@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/
RE: Unable to dump repository
Posted by Tony Thompson <To...@stone-ware.com>.
On 3/15/07, Tony Thompson <To...@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.
Thanks for your help.
Tony
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.
Re: Unable to dump repository
Posted by Mark Phippard <ma...@gmail.com>.
On 3/15/07, Tony Thompson <To...@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
RE: Unable to dump repository
Posted by Tony Thompson <To...@stone-ware.com>.
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.
________________________________
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Thursday, March 15, 2007 1:38 PM
To: Tony Thompson
Cc: users@subversion.tigris.org
Subject: Re: Unable to dump repository
On 3/15/07, Tony Thompson <To...@stone-ware.com> wrote:
I have gotten my repository into such a state that I cannot do
an "svnadmin dump" or "svnadmin verify". I get an error message back
that says:
svnadmin: Filesystem path 'tags/v5.1.0.2' is neither a file nor
a directory
This happened after I had an issue after I deleted a tagged
revision out of the repository. I have the tags/v5.1.0.2 directory back
in the repository but apparently something is already corrupted. I am
still able to do a hotcopy but that doesn't help me because the copy is
corrupted as well. I am using v1.4.3.
Is there a way I can repair the repository?
Does verify report a specific bad revision? If so, you ought to be able
to dump your repository up to that revision.
--
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.
Re: Unable to dump repository
Posted by Mark Phippard <ma...@gmail.com>.
On 3/15/07, Tony Thompson <To...@stone-ware.com> wrote:
>
> I have gotten my repository into such a state that I cannot do an
> "svnadmin dump" or "svnadmin verify". I get an error message back that
> says:
>
> svnadmin: Filesystem path 'tags/v5.1.0.2' is neither a file nor
> a directory
>
> This happened after I had an issue after I deleted a tagged revision out
> of the repository. I have the tags/v5.1.0.2 directory back in the
> repository but apparently something is already corrupted. I am still able
> to do a hotcopy but that doesn't help me because the copy is corrupted as
> well. I am using v1.4.3.
>
> Is there a way I can repair the repository?
>
Does verify report a specific bad revision? If so, you ought to be able to
dump your repository up to that revision.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/