top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

SVN crash with large repository?

+3 votes
306 views

I've just had SVN crash. I'm working on a fairly large repository (probably around 60gb or so) and was in the process of checking it out. The HDD ran out of space, which caused SVN to stop gracefully. After calling svn clean up, I called svn up, got a handful of files and then it crashed.

posted Jul 25, 2016 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
I am not sure, why you are using svn for this type of large repository, anyway you can try to use git, It working absolutely perfect with large repository.

Similar Questions
0 votes

I am using subversion (version 1.9.4 (r1740329)) on centos 6..6
have created empty repository. and restored backup (hotcopy)
after restoring backup I am getting following error

Cant read file /svn/test/db/uuid: End of file found

tried searching for such errors but searches found refer to db/current or db/txn-current
I can not use any option svnadmin setuuid or svnlook uuid

How to resolve this issue ?

+1 vote

I would like to use Git with a SVN, so I try to clone the SVN repo with "git svn clone svn://myserver", it is a repo without trunk etc. Git reports the error "Couldn't find a repository". The SVN repo uses an authentification (username & password) and a normalsvn checkout works well.
How can I use the SVN repo with Git?

+1 vote

I have 30 files that I want to merge, but I do not know which would be the easiest and much efficient and save way to do so.
I have the main production line Z and two other branches X and Y. All of the branches are still in production since X and Y are minor releases. Therefor on a time frame they are look this:
Z - trunk, next major releaseY - next minor release (Z - Y = small changes)X - used to make patches for an old release
The idea is that between Z and Y arent so many differences, but between X and Y(or Z) are plenty. There was a fix in the X branch that needs to be back ported into Z and Y. I am using svn merge to merge changes from X to Y, but because of the big differences I think it adds even code that could not be useful in Y, showing as conflicts just a few code blocks/file. which would be the best approach for such a merge?

+2 votes

Recently we have installed SVN in a new windows server.

Migrated and loaded the users repositories in the new SVN server. I could able to access those repositories. Created users, but could not able to access those repository, login is not accepting and it prompts continuously.

We are using Tortoise SVN as front end GUI. Kindly assist me on this.

...