Re: corrupt tree/transaction

On Thursday 22 April 2010, Php freaked wrote:
> I was using subversion until it reported me it ran out of disk-space. It
> turns out the svn repository was configured at the smallest disk, so
> logically I move the svn repository to other hard-drive. But ever since I
> move it I've been unable to commit in my repository. To give you an idea of
> what I did:
>
>
> cp /path/to/oldrepository/ /path/to/newrepository/
> mv /path/to/oldrepository/ /path/to/oldrepository2/ //for
> backup purposes
> mount --bind /path/to/oldrepository/ /path/to/newrepository/
>
> By mouting the folder to a folder I could preserve all existing
> configuration paths. As one can see I used the 'cp' command to copy the
> files, I was told in #svn_at_freenode.net I should have used svn hotcopy. At
> the time I was unaware of this, I presumed svn worked atomically on it's
> files.

Well, it was "cp" and "mv" working on SVN's files! Anyway, if nothing was
accessing the repository at the time, you should be fine.

> After that I initially tried to commit my files and I received the
> error 'Commit failed (details follow):Cannot write to the prototype
> revision file of transaction '228-1' because a previous representation is
> currently being written by this process'
>
> I checked if there was such a transaction open using svnadmin lstxns And it
> reported me there was indeed a transaction open but this one was 154-1. So
> I removed the transaction, somewhere hoping it would resolve the issue but
> as expected it didn't work. So somebody from the irc channel suggested me
> to try dump/load to a clean repository, which i did.
>
> svnadmin create /path/to/newrepo2/
> svnadmin dump /path/to/newrepo/ -r 0:227 > backup.dump
> svnadmin load /path/to/newrepo2/ < backup.dump
>
> After that I tried to commit some files e.g. I did a svn checkout,
> reapplied my changes and tried to commit them. Either in partial commits or
> multiply files at once the error persists. I've already tried removing
> pending transactions, the /db/revprops/228 appears not the be in there.
> What should I do? Here's some additional information: rev 0-227 historical
> commits, rev 228 last working revision, 229 would be the supposed new
> revision.

Maybe the issue is permissions and the error is just misleading. The process
writing to the repository needs full read and write access. BTW: What method
do you use to access the repository?

BTW: You shouldn't have to check out a new working copy. If the URL of the
repository changed, you would only have to use "svn switch --relocate ..." to
adjust to that. However, due to the link you made, you shouldn't even have to
do that.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************