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 & Mikaela Krueger <in...@michael-krueger.org> on 2006/05/06 22:03:05 UTC
Unable to access repository, please help...
Hi,
I run a Linux server (SuSE 9.2) with Subversion that came with it... 1.2
something I would say.
I have a server directory under:
/srv/svn/repos/
in which all of my repositories reside.
Now one of my repositories (actually the most important one) seems to be
broke.
Most of the times when one of the repositories reports a berkley DB error in
ViewCVS, a quick svnadmin recover <repository> does a quick job fixing any
issues. This time it doesn't.
Any SVN command, be it svnadmin, svn, svnlook that I execute on that
repository will just hang. I'm not able to recover it. Does anyone have
expirience with this? Anyone able to recommend a solution to recover the
project?
--
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to access repository, please help...
Posted by Michael & Mikaela Krueger <in...@michael-krueger.org>.
Well I now somewhat know what you mean...
I installed the 1.3.1 version and the apache modules do not load ... so I may
have to upgrade apache too... what a pain ...
So it may make sense to upgrade the server anyway...
Btw. the repository doesn't recover with the new version of the binaries. The
berkley db recover tool does say something that I don't understand. But it
didn't look serious to me. I may try to recover that one later on. For now
the plan is to upgrade the server, create new FSFS repositories and load the
dump from the old ones into them.
That should fix it hopefully.
Michael
Am Montag, 8. Mai 2006 00:27 schrieb Nico Kadel-Garcia:
> Michael & Mikaela Krueger wrote:
> > Hmm...
> > Ok I understand that I should upgrade to Subversion 1.3.1... I don't
> > understand why I should upgrade the whole SuSE system...
>
> Despite SuSE's claim of "we will support our OS's for seven years, there is
> very little excuse for staying 2 major revisions behind the current
> release. There are numerous tools, such as apr, swig, neon, and httpd that
> would all benefit from the upgrades and all of which are part of
> Subversion's requirements. It is painful to try and backport versions that
> may be required for the current subversion to go back that far: my advice
> for is if you don't have a compelling reason to do so, don't bother, just
> do forklist updates.
>
> > And will the 1.3.1 be able to recover my broken repository?
>
> Good question. I can't guarantee that without actually playing with your
> setup myself, but I think you'll have a much better chance at it.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
--
Michael & Mikaela Krüger
Email: info@michael-krueger.org
Web: www.michael-krueger.org
ICQ: 278-333-735
Skype: mmckrueger
PGP-Fingerprint: C1AA 9D0A A62F 5742 2AA6 53BD 54C6 AF11 0B95 BC49
Key-ID: 0B95BC49
--
To mess up a Linux box, you need to work at it;
to mess up your Windows box, you just need to work on it.
Scott Granneman, Security Focus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to access repository, please help...
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Michael & Mikaela Krueger wrote:
> Hmm...
> Ok I understand that I should upgrade to Subversion 1.3.1... I don't
> understand why I should upgrade the whole SuSE system...
Despite SuSE's claim of "we will support our OS's for seven years, there is
very little excuse for staying 2 major revisions behind the current release.
There are numerous tools, such as apr, swig, neon, and httpd that would all
benefit from the upgrades and all of which are part of Subversion's
requirements. It is painful to try and backport versions that may be
required for the current subversion to go back that far: my advice for is if
you don't have a compelling reason to do so, don't bother, just do forklist
updates.
> And will the 1.3.1 be able to recover my broken repository?
Good question. I can't guarantee that without actually playing with your
setup myself, but I think you'll have a much better chance at it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to access repository, please help...
Posted by Michael & Mikaela Krueger <in...@michael-krueger.org>.
Hmm...
Ok I understand that I should upgrade to Subversion 1.3.1... I don't
understand why I should upgrade the whole SuSE system...
And will the 1.3.1 be able to recover my broken repository?
Michael
Am Sonntag, 7. Mai 2006 01:48 schrieb Nico Kadel-Garcia:
> Michael & Mikaela Krueger wrote:
> > Hi,
> >
> > I run a Linux server (SuSE 9.2) with Subversion that came with it...
> > 1.2 something I would say.
> > I have a server directory under:
> > /srv/svn/repos/
> > in which all of my repositories reside.
> > Now one of my repositories (actually the most important one) seems to
> > be broke.
> > Most of the times when one of the repositories reports a berkley DB
> > error in ViewCVS, a quick svnadmin recover <repository> does a quick
> > job fixing any issues. This time it doesn't.
> > Any SVN command, be it svnadmin, svn, svnlook that I execute on that
> > repository will just hang. I'm not able to recover it. Does anyone
> > have expirience with this? Anyone able to recommend a solution to
> > recover the project?
>
> Yes. Take it offline, back it up if possible, do a hot-copy.py backup as
> well if possible, then update your SuSE to 10.0 and your Subversion to
> 1.3.1.
>
> SuSE makes claims that they will support a release for 7 years, but *who
> cared!!!*? The differences in kernel and database tools between 9.2 and 9.3
> alone justify the upgrade, going to 10.0 should just sweeeten the deal. And
> subversion 1.3.1 gets you a stack of useful new features.
>
> Even better, after your OS and subversion is updated, switch the back-end
> database from Berkeley DB to FSFS for better reliability. BDB was cool, but
> it's overpowered for Subversion use, and very difficult to repair corrupted
> databases. And the company that made it, Sleepycat, was recently purchased
> by Oracle. I think we can expect Oracle to ruin it within 2 years the same
> way they trashed the Stettor calendar server. Many open source tools have
> moved away from BDB for various reasons: cross-platform use for Subversion
> helped drive the use of FSFS as the new default database.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
--
Michael & Mikaela Krüger
Email: info@michael-krueger.org
Web: www.michael-krueger.org
ICQ: 278-333-735
Skype: mmckrueger
PGP-Fingerprint: C1AA 9D0A A62F 5742 2AA6 53BD 54C6 AF11 0B95 BC49
Key-ID: 0B95BC49
--
To mess up a Linux box, you need to work at it;
to mess up your Windows box, you just need to work on it.
Scott Granneman, Security Focus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Unable to access repository, please help...
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Michael & Mikaela Krueger wrote:
> Hi,
>
> I run a Linux server (SuSE 9.2) with Subversion that came with it...
> 1.2 something I would say.
> I have a server directory under:
> /srv/svn/repos/
> in which all of my repositories reside.
> Now one of my repositories (actually the most important one) seems to
> be broke.
> Most of the times when one of the repositories reports a berkley DB
> error in ViewCVS, a quick svnadmin recover <repository> does a quick
> job fixing any issues. This time it doesn't.
> Any SVN command, be it svnadmin, svn, svnlook that I execute on that
> repository will just hang. I'm not able to recover it. Does anyone
> have expirience with this? Anyone able to recommend a solution to
> recover the project?
Yes. Take it offline, back it up if possible, do a hot-copy.py backup as
well if possible, then update your SuSE to 10.0 and your Subversion to
1.3.1.
SuSE makes claims that they will support a release for 7 years, but *who
cared!!!*? The differences in kernel and database tools between 9.2 and 9.3
alone justify the upgrade, going to 10.0 should just sweeeten the deal. And
subversion 1.3.1 gets you a stack of useful new features.
Even better, after your OS and subversion is updated, switch the back-end
database from Berkeley DB to FSFS for better reliability. BDB was cool, but
it's overpowered for Subversion use, and very difficult to repair corrupted
databases. And the company that made it, Sleepycat, was recently purchased
by Oracle. I think we can expect Oracle to ruin it within 2 years the same
way they trashed the Stettor calendar server. Many open source tools have
moved away from BDB for various reasons: cross-platform use for Subversion
helped drive the use of FSFS as the new default database.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org